Article on the branch strategy in gitworkflows(7)

Raman Gupta· Mar 22, 2017, 16:41 UTC · lore

Several years ago, I contributed [1] to the gitworkflows(7) documentation, because I thought the process by which git.git does branching was really interesting.

Since then, I have found it odd that gitworkflows has mostly remained under the radar. Other, in my opinion, lesser flows, have become very popular, like GitFlow [2]. I have written an article explaining the "why" of gitworkflow in contrast to GitFlow and others:

https://docs.google.com/document/d/1cGNujRNVzeLV2SXkVlKwai6qJmlVT3LwlOsVYNr0FZo/edit?usp=sharing

This article is not published yet -- its still a DRAFT and only visible via the above URL.

I'd love to have input on the draft from the experts in this community. Feel free to suggest changes and add comments in the article via Google Docs.

Also, some explanatory illustrations to accompany the article would be excellent, if anyone feels like contributing. Visuals are not my strong suit. I'd love to include something similar to the graphic [3] that was a big part of making GitFlow so popular. The article can be partially rewritten to match illustrations, if any are contributed.

[1] https://github.com/git/git/commit/382e54312220ac02586a3cbb06b0e4eb7789f043

[2] http://nvie.com/posts/a-successful-git-branching-model/

[3] http://nvie.com/img/git-model@2x.png

Regards, Raman Gupta

Raman Gupta· May 11, 2017, 15:56 UTC · re: Raman Gupta · lore

Re: Article on the branch strategy in gitworkflows(7)

FYI - the article mentioned below has been published @ https://medium.com/@ramangupta/how-the-creators-of-git-do-branches-e6fcc57270fb

Thank you to the two or three people that I know of that took the time to read the draft.

Regards, Raman

On 22/03/17 12:41 PM, Raman Gupta wrote:

Show 34 quoted lines

> Several years ago, I contributed [1] to the gitworkflows(7)
> documentation, because I thought the process by which git.git does
> branching was really interesting.
> 
> Since then, I have found it odd that gitworkflows has mostly remained
> under the radar. Other, in my opinion, lesser flows, have become very
> popular, like GitFlow [2]. I have written an article explaining the
> "why" of gitworkflow in contrast to GitFlow and others:
> 
> https://docs.google.com/document/d/1cGNujRNVzeLV2SXkVlKwai6qJmlVT3LwlOsVYNr0FZo/edit?usp=sharing
> 
> This article is not published yet -- its still a DRAFT and only
> visible via the above URL.
> 
> I'd love to have input on the draft from the experts in this
> community. Feel free to suggest changes and add comments in the
> article via Google Docs.
> 
> Also, some explanatory illustrations to accompany the article would be
> excellent, if anyone feels like contributing. Visuals are not my
> strong suit. I'd love to include something similar to the graphic [3]
> that was a big part of making GitFlow so popular. The article can be
> partially rewritten to match illustrations, if any are contributed.
> 
> [1]
> https://github.com/git/git/commit/382e54312220ac02586a3cbb06b0e4eb7789f043
> 
> [2] http://nvie.com/posts/a-successful-git-branching-model/
> 
> [3] http://nvie.com/img/git-model@2x.png
> 
> Regards,
> Raman Gupta
>