Created
March 27, 2019 18:11
-
-
Save ShaunMerritt/895701a0a15abd3bdda473503e7852eb to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What is gitflow: | |
“Vincent Driessen’s "git flow" branching model is a git branching and release management workflow that helps developers keep track of features, hotfixes and releases in bigger software projects.” | |
Basically, gitflow is a structured way of branching that doesn’t get in the way of developers making features. | |
It works by having specific branches and branching structure with different intentions. The structure is: | |
Master (Always reflects what is in the App Store) | |
Hotfixes (Urgent fixes to things that are in Master) | |
Releases (Ready for release, only bug fixes go into these) | |
Develop (Default branch where most work will happen) | |
Features (New features or tickets) | |
Gitflow Benefits: | |
* Multiple branches allows for flexibility but structure helps keep things from becoming complicated | |
* Structure makes sure everyone can jump in at any point. | |
* Easy hot fixes | |
* Defines what to do when multiple releases are going at the same time | |
* Makes it easy for new hires to come in and know what the release process is | |
Useful Links With Examples: | |
https://jeffkreeftmeijer.com/git-flow/ | |
https://github.com/nvie/gitflow | |
https://github.com/bobthecow/git-flow-completion |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment