Re: [PATCH v2] status: compare against both upstream and push branch by default

From: Harald Nordgren <haraldnordgren@gmail.com>
Date: Oct 23, 2026, 18:48 UTC
Message-ID: <CAHwyqnVMgAhyHrevXOJ0sBKkaPPzSmCcCPSSeqm6dm-MRX65cQ@mail.gmail.com>
In-Reply-To: <xmqqld7o71ot.fsf@gitster.g>

> I do not think I follow.  Those who are just starting to push to a
> destination other than @{upstream} would have changed their
> configuration to do so, wouldn't they?  Aren't they equally well
> placed, if not more, to find the same setting?

Most users (from my experience) have their *push* branch as upstream, stemming from the `git push -u` behavior that is recommended by GitHub. Meaning they are already missing the info about what upstream is doing and how it’s changing.

This is limiting their understanding of triangular workflows.

When using `--set-upstream-to`, now they get upstream status, a big improvement, but this scares many users because the connection to push branch is now seemingly lost.

This is the point behind this: To ease users into triangular thinking. We should not assume our users are git experts, many of my them never read the git docs.

Harald