Re: [RFC] Triangular Workflow: user friendly full implementation
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 26, 2016, 18:30 UTC
- Message-ID
- <xmqqwpmgvfif.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <E83A9439-54C8-4925-8EE3-6AEEDD9416F3@grenoble-inp.org>
Jordan DE GEA <jordan.de-gea@grenoble-inp.org> writes:
Show 5 quoted lines
> We are working on full implementation of triangular workflow feature. > For now, the main options available are: > - branch.<name>.pushRemote > - remote.pushDefault > And only setable by hands.
And once it is set, you do not have to worry about it. I am not sure per-branch thing is all that useful, unless you are always working on a single branch like 'master', but the latter would be just set once and forget about it.
Show 7 quoted lines
> Context: > - One main remote repository, e.g. git/git. > - A remote fork (e.g. a GitHub fork) of git/git, e.g. me/git. > - A local clone of me/git on the machine > Purposes: > - the local branch master has to fetch to git/git by default > - the local branch master has to push to me/git by default
Wouldn't remote.pushDefault be the single thing you need to set just once and forget about it? Why would your users even want to do these things ...
Show 6 quoted lines
> c. add `git fetch --set-default` in order to set remote.fetchDefault > d. add `git fetch --set-remote` in order to set branch.<name>.fetchRemote > e. add `git pull --set-default` in order to set remote.fetchDefault > f. add `git pull --set-remote` in order to set branch.<name>.fetchRemote > a. add `git push --set-default` in order to set remote.pushDefault > b. add `git push --set-remote` in order to set branch.<name>.pushRemote
... just to configure many variables every time they work on a new branch?