Menu
in gitflow all release branches are eventually
but why don't we just
in case of hotfix we can just
240
A branch in Git is simply a lightweight movable pointer to one of these commits. The default branch name in Git is master . As you start making commits, you're given a master branch that points to the last commit you made. Every time you commit, the master branch pointer moves forward automatically.
Git Flow Workflow simplifies parallel development because it isolates the new development from the released project. You can work on any project version. The new development is done in feature branches so it is merged back when the developer is satisfied with the code.
Most Git repositories use master as the main (and default) branch - if you initialize a new Git repo via git init , it will have master checked out by default.
One word: the master branch is deployable. It is your production code, ready to roll out into the world. The master branch is meant to be stable, and it is the social contract of open source software to never, ever push anything to master that is not tested, or that breaks the build.
You are almost describing a release-flow branching model:
There is no final merge to a production branch - its not needed as the release branch is the same thing.
Once an old release branch has been superceeded by the next one it can be deleted if no longer required for audit purposes.
This is documented well by the VSTS team: https://docs.microsoft.com/en-gb/azure/devops/devops-at-microsoft/release-flow
148
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
