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

#git #gitflow #githubflow

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

https://t.co/lcdykCpBQF

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?

#swDevTermOfTheDay #GithubFlow is a branching model for the git #VCS where the master is always deployable, new work is done on local+remote branches off master, a #PullRequest (#PR) is opened before merging to master and merged to master once the #PR is approved.