Advertisement
Guest User

Untitled

a guest
Dec 8th, 2016
97
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.22 KB | None | 0 0
  1. # Create a feature branch
  2. # Typically, branch from the current develop branch:
  3.  
  4. git fetch
  5. git checkout develop.xx
  6. git pull origin develop.xx
  7.  
  8. git checkout -b <BRANCH_NAME>
  9. # Make atomic commits
  10. git add .
  11. git commit -m "Did something awesome."
  12. # Squash commits
  13. # When development is complete, squashing tidies up history and makes rebasing much easier.
  14. git rev-list --count HEAD ^SPRINT_XX
  15. git rebase -i HEAD~X
  16. # where X is the number of commits made on the development branch (you can get this by using the rev-list call on the line above)
  17.  
  18. # Rebase against the develop branch
  19. git checkout develop.xx
  20. git pull origin develop.xx
  21. git checkout -
  22. git rebase develop.xx
  23. # Manage any conflicts. Then, ensure that all tests still pass and that the application still works as expected.
  24.  
  25. # Or you can squash commits here, if you did not do it before rebase to develop.xx branch
  26. git rebase -i develop.xx
  27.  
  28. # Push the branch
  29. git push -f origin <BRANCH_NAME>
  30. # Create a pull request
  31. # Action any changes that come out of the code review, making sure to again squash and rebase once these have been done.
  32.  
  33. # The pull request should not be merged by the developer who has raised it. Paste the link to the PR into a Skype chat if you need it actioned quickly.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement