Re: git branch --edit-description a custom file
- From
Philip Oakley <philipoakley@iee.email>
- Date
- Oct 31, 2019, 13:45 UTC
- Message-ID
- <9aa1cefc-daeb-e702-95ba-1e83f8f7dcfe@iee.email>
- In-Reply-To
- <nycvar.QRO.7.76.6.1910311229150.46@tvgsbejvaqbjf.bet>
Hi, On 31/10/2019 11:30, Johannes Schindelin wrote:
Show 7 quoted lines
> And while we're dreaming: it would be nice to discern between "push > upstreams" and "base upstreams". Example: when I work on the > `fix-t5516-flakiness` branch, I target `upstream/master`, but I push to > `dscho`, i.e. my "push upstream" is `dscho/fix-t5516-flakiness`. > > Ciao, > Dscho
Yep, the triangular workflow of 'publish' v 'upstream' v 'local' is quite tricky. There is little user facing docs for that.
Many of my branches have the wrong "upstream" in the sense that it's the push-publish remote that holds copies of my work (i.e. I manually select the push-remote every time;-), even though the branches are set to track the original start point's upstream.
Philip