Alex Henrie <alexhenrie24@xxxxxxxxx> writes: >> When you start working on your own topic forked from upstream by >> switching to it, if Git notices that your topic's base has become >> behind (so that you would later need to merge or rebase to avoid >> losing others' work), the "git pull" message is given to tell you >> that it is OK if you want to catch up first before working on it. >> >> But the new message does not fit well in the workflow. It is >> primarily targetted for the users who are about to push out. They >> are at the point where they are way before being ready to "discard >> the work at the remote". > > If the branch is merely behind, format_tracking_info prints "(use "git > pull" to update your local branch)", which is perfectly reasonable. Correct. The message you are changing is not the "your topic has become behind" case, and it is exactly why I said "your topic's base has become behind", i.e. your upstream has diverged. > The problem is only with the message that appears when the branches > are divergent, "(use "git pull" to merge the remote branch into > yours)", which is bad advice for the common GitHub/GitLab workflow > that expects force-pushing. We are in agreement in that "you must always reconcile" is not a good message in general to give, but I do not think "git checkout" and "git status" are good places to give the new advice "depending on your workflow, you do not necessarily have to pay attention to what the upstream has and just overwrite it may be good". That is about how to "push", but the user is a few steps before they are ready to start thinking about how to "push" when they get this message. These places in "checkout" and "status", where the message is given, were perfectly good places to say "by the way, you are divergent and even long before you are ready to push your work out, you may want to refresh your work to work better with the updated upstream", which was the "use git pull to reconcile" message was all about.
