Choose Git Flow for structured, versioned releases or GitHub Flow for continuous deployment based on your team's deploy frequency and release cycle needs.
https://dev.to/hongster85/git-flow-vs-github-flow-understand-in-3-minutes-kmm
The #Agile, the #Fragile, and the Iron Fist of #Branching Strategies
https://www.diversion.dev/blog/the-agile-the-fragile-and-the-iron-fist-of-branching-strategies
Whether you love it or hate it, Git has proven to be the nearly ubiquitous method engineering organizations employ to ship code today. However, when you’re just getting started and building your team, you may be thinking about which strategy is the right one for you to choose based on your current and future needs.
Post do Igor com boa visão, e concordo com a recomendação dele no final do artigo.
---
RT @igorabade
Na sua empresa usa-se Git Flow para estruturar o processo de versionamento de código? Então deixa eu te dar uma má notícia: provavelmente vocês tomaram uma decisão (bem) ruim...
#azuredevops #azurerepos #devops #git #gitflow #github #githubflow
https://www.cloudmotion.com.br/blog/2023/04/19/usando-gitflow-oops/
https://twitter.com/igorabade/status/1651239769983131650
Na sua empresa usa-se Git Flow para estruturar o processo de versionamento de código? Então deixa eu te dar uma má notícia: provavelmente vocês tomaram uma decisão (bem) ruim...
#azuredevops #azurerepos #devops #git #gitflow #github #githubflow
I've read some articles about #TrunkBasedDevelopment versus #GitFlow / #GithubFlow. In short, TBD is about not having long-lived feature branches but all developers daily sending their changes to an always releasable main branch, this to avoid merge conflicts and to speed up continuous delivery.
What do you think about branching versus trunk based?
er2klc
Hongster
Nicolas Fränkel 🇪🇺🇺🇦🇬🇪
Giovanni Bassi
Igor Abade
Jon Arvid
Michael Hönnig