3 ms·
Is this related to the "Please stop recommending Gitflow" [1] article posted yesterday? [1] https://news.ycombinator.com/item?id=22485489 https://news.ycombina
by gulbrandr 7y ago
Is this related to the "Please stop recommending Gitflow" [1] article posted yesterday?
[1] https://news.ycombinator.com/item?id=22485489 https://news.ycombinator.com/item?id=22485489
- deleted 7y ago[deleted]
- sytse 7y agoKind of, that article recommends making things less complex if you do continuous delivery to a SaaS. The update article mentions it was meant for versioned software. I tried to articulate the various levels of branching you need in GitLab Flow https://docs.gitlab.com/ee/topics/gitlab_flow.html https://docs.gitlab.com/ee/topics/gitlab_flow.html The various levels are: feature branches, production branches, environment branches, and release branches.
- waheoo 7y agoSounds like gitlab tried to fix githubflow instead of realising its fundamentally broken and going with the gerrit pattern that works fine for both trunk based and release style applications.
- sytse 7y agoWe offer multiple options that depend on your need. GitHub flow and Git flow are at two ends but there are also intermediate steps.