Git Workflow with Gitflow
What is a workflow? "...consists of a sequence of connected steps.." - Wikipedia What are we looking?             An way t...
GitFlow
Why Gitflow?    ■ Based on the graph you just saw.    ■ Github - https://github.com/nvie/gitflow    ■ Shortcuts for repeti...
Main branches    1. master -> production-ready    2. develop -> latest for next release    Their lifetime is infinite.
Gitflow - prepare repository  $git flow init  When creating a new git flow workflow it ask you questionsthe names of the b...
Gitflow - Supporting branches  There are 4 supporting branches:        1. feature        2. release        3. hotfix      ...
Gitflow - Feature branches● May branch off from: develop branch● Must merge back into: develop branch● Branch naming conve...
Gitflow - Create feature branches$git flow feature start 3base_<issue #>_<feature name>This is what it does:$git checkout ...
Gitflow - finish feature branch ● git flow feature finish <feature name>$git checkout develop$git merge --no-ff myfeature ...
More on the subject   ● gitflow on github -https://github.com/nvie/gitflow.   ● A successful git branching model   ● A sho...
Git Workflow With Gitflow
Git Workflow With Gitflow
Git Workflow With Gitflow
Git Workflow With Gitflow
Upcoming SlideShare
Loading in...5
×

Git Workflow With Gitflow

2,243

Published on

Published in: Technology
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,243
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
29
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Transcript of "Git Workflow With Gitflow"

  1. 1. Git Workflow with Gitflow
  2. 2. What is a workflow? "...consists of a sequence of connected steps.." - Wikipedia What are we looking? An way to multiple developers integrate a working code into a project
  3. 3. GitFlow
  4. 4. Why Gitflow? ■ Based on the graph you just saw. ■ Github - https://github.com/nvie/gitflow ■ Shortcuts for repetitive tasks. ■ Branch naming convention "<prefix>/<name>" ■ 2 main branches.
  5. 5. Main branches 1. master -> production-ready 2. develop -> latest for next release Their lifetime is infinite.
  6. 6. Gitflow - prepare repository $git flow init When creating a new git flow workflow it ask you questionsthe names of the branches - USE DEFAULTS. when this is done a new develop branch is createdfrom master and from this point you never commit tomaster branch anymore.
  7. 7. Gitflow - Supporting branches There are 4 supporting branches: 1. feature 2. release 3. hotfix 4. support I will cover only feature since this is the only one you willwith.
  8. 8. Gitflow - Feature branches● May branch off from: develop branch● Must merge back into: develop branch● Branch naming convention: anything except master, develop, release/*, hotfix/* - our branching name will consist with 3base_<issue #>_<feature name>● Typically exist in developer repos only, not in origin - from time to time I will ask to also push the specific branch also to origin.
  9. 9. Gitflow - Create feature branches$git flow feature start 3base_<issue #>_<feature name>This is what it does:$git checkout -b feature/3base_<issue #>_<feature name> develop
  10. 10. Gitflow - finish feature branch ● git flow feature finish <feature name>$git checkout develop$git merge --no-ff myfeature - merges the branch to develop.$git branch -d myfeature - deletes the local branch$git push origin develop - push develop.The --no-ff flag avoids losing information about the historicalexistence of a feature
  11. 11. More on the subject ● gitflow on github -https://github.com/nvie/gitflow. ● A successful git branching model ● A short introduction to git-flow ● On the path with git-flow
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×