Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

9.
Gitflow Workflow
Gitflow
• Release Branches
• When develop branch has enough features for a release it’s time to
create a new branch from develop – Release Branch
• This action starts a new release cycle
• New feature can’t be added
• Only can be added bug fixes, documentation and tasks
related with the release process
• When the release is ready to deliver, the release branch should be
merged into master and develop and a new tag should be created.

10.
Gitflow Workflow
Gitflow
• Maintenance Branches
• Also known as a hotfix branch
• Unique branch that should be created from master branch
• When the fix is complete, the branch should be merged into master
and develop or the current release branch
• Master branch should be tagged with the current version

12.
Forking Workflow
Forking Workflow
• It’s different from other workflows already presented here
• There is no central repository
• Each developer has a server-side repository (public) and a local repository
(private)
• Developers push to their own server-side repositories
• Only the project maintainer can push to the official repository
• In this way, project maintainer accept commits from any developer without
giving them access to the official codebase
• Bitbucket and Github are examples of using this workflow.