Understanding Branches in Git (why master and development....)

PHOTO EMBED

Mon Nov 16 2020 19:44:54 GMT+0000 (UTC)

Saved by @ali_alaraby

The central repo holds two main branches with an infinite lifetime:

master
develop
The master branch at origin should be familiar to every Git user. Parallel to the master branch, another branch exists called develop.

We consider origin/master to be the main branch where the source code of HEAD always reflects a production-ready state.

We consider origin/develop to be the main branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release. Some would call this the “integration branch”. This is where any automatic nightly builds are built from.

When the source code in the develop branch reaches a stable point and is ready to be released, all of the changes should be merged back into master somehow and then tagged with a release number. How this is done in detail will be discussed further on.

Therefore, each time when changes are merged back into master, this is a new production release by definition. We tend to be very strict at this, so that theoretically, we could use a Git hook script to automatically build and roll-out our software to our production servers everytime there was a commit on master.
content_copyCOPY

https://nvie.com/posts/a-successful-git-branching-model/