Understanding Git Workflow Models and Branching Strategies
Explore the comprehensive Git workflow model and branching strategies by Vincent Driessen, covering main branches, feature branches, release branches, hotfix branches, and support branches. Learn how to structure your repository for efficient collaboration and version control.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
A Git Workflow Model Slides produced from blog by Vincent Driessen http://nvie.com/git-model and secondary posting at http://gist.github.com/287237
The big picture Original blog by Vincent Driessen http://nvie.com/git-model
Repository relationships http://nvie.com/git-model
Main branches master used for production releases develop used for integration and regression testing http://nvie.com/git-model
Feature branches http://nvie.com/git-model
Release branches Branched from develop when it almost reflects the desired new release Bug fixes for the release are applied here No new features may be added to this branch New feature development can continue in parallel on the develop branch
Hotfix Branches Are like release branches, but for bug fixes http://nvie.com/git-model
Support Branches If master has moved on to a new and a hotfix must be applied to a older version ( e.g 1.x): create a support-1.x branch (if none exists) based on the newest 1.x tag in master create a branch (e.g. hotfix-1.1.1), based on support-1.x fix the bug and merge hotfix-1.1.1 back into support-1.x Do this for other older major releases as necessary The support branch effectively becomes a master branch for a past version.
