git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[RFC] Triangular Workflow: user friendly full implementation

From
JGJordan DE GEA <jordan.de-gea@grenoble-inp.org>
Date
May 26, 2016, 10:06 UTC
Message-ID
<E83A9439-54C8-4925-8EE3-6AEEDD9416F3@grenoble-inp.org>
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. 
As it can be difficult to understand, here is what we want to do. 
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
Configuration wanted:
	- Add a remote to git/git e.g. `git remote add ...`
	- Set the fetch remote for branch as default. 
For now, we can do that by setting: 
	- branch.<name>.remote to git/git
	- branch.<name>.pushRemote to me/git
But many options set `branch.<name>.remote`, a suitable solution is to
implement an option for the fetch for example. 
Here is what we want to implement: 
1. 
	a. add the config var: remote.fetchDefault
	b. add the config var: branch.<name>.fetchRemote
	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
2. 
	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
What's your opinion about this feature ?
Next: Matthieu Moy
Message 1 of 41 in “[RFC] Triangular Workflow: user friendly full implementation”
  1. Jordan DE GEAMay 26, 2016
  2. Matthieu MoyMay 26, 2016
  3. Junio C HamanoMay 26, 2016
  4. [RFC] Triangular Workflow UI improvementJordan DE GEA, May 30, 2016
  5. Philip OakleyMay 27, 2016
  6. [RFC] Triangular Workflow UI improvmentsJordan DE GEA, May 30, 2016
  7. Triangular Workflow UI improvement: DocumentationJordan DE GEA, May 31, 2016
  8. Matthieu MoyMay 31, 2016
  9. Jordan DE GEAJun 1, 2016
  10. Michael HaggertyJun 2, 2016
  11. Philip OakleyJun 3, 2016
  12. Jordan DE GEAJun 3, 2016
  13. Matthieu MoyJun 3, 2016
  14. Jordan DE GEAJun 3, 2016
  15. Jordan DE GEAJun 5, 2016
  16. Matthieu MoyJun 6, 2016
  17. Philip OakleyJun 6, 2016
  18. Matthieu MoyJun 6, 2016
  19. Philip OakleyJun 6, 2016
  20. Matthieu MoyJun 7, 2016
  21. Philip OakleyJun 7, 2016
  22. Junio C HamanoJun 3, 2016
  23. Philip OakleyJun 3, 2016
  24. [RFC/PATCHv2] Documentation: triangular workflowJordan DE GEA, Jun 6, 2016
  25. Junio C HamanoJun 6, 2016
  26. Philip OakleyJun 6, 2016
  27. Matthieu MoyJun 7, 2016
  28. Jordan DE GEAJun 7, 2016
  29. [PATCHv3] Documentation: triangular workflowJordan DE GEA, Jun 7, 2016
  30. Junio C HamanoJun 7, 2016
  31. Jordan DE GEAJun 8, 2016
  32. Matthieu MoyJun 8, 2016
  33. [PATCHv4] Documentation: triangular workflowJordan DE GEA, Jun 9, 2016
  34. Junio C HamanoJun 9, 2016
  35. Ramkumar RamachandraJun 11, 2016
  36. Philip OakleyJun 11, 2016
  37. Philip OakleyJun 9, 2016
  38. Junio C HamanoJun 10, 2016
  39. Philip OakleyJun 11, 2016
  40. Junio C HamanoJun 13, 2016
  41. [RFC] Triangular Workflow UI improvementJordan DE GEA, May 30, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.