git checkout release\r\ngit pull upstream release\r\ngit push origin release\r\ngit checkout -b [branch name]<\/pre>\nWorkflow<\/h3>\n
As previously stated, when works starts on a new task\/story, a new branch is created from the release branch. You will develop and commit in this branch until you\u2019re done. You are encouraged to commit as often as possible:<\/p>\n
git add [file to be commited]\r\ngit commit -m \u201ccommit message\"\r\ngit push origin [branch name]<\/pre>\nWe recommend to check what is to be committed first, by running the git status<\/code> and git diff<\/code> commands, then adding each file individually (or group of files) to the commit.<\/p>\n![\"face-glasses\"](\"\/\/intelligentbee.com\/blog\/wp-content\/uploads\/2015\/03\/face-glasses.png\")
Avoid adding\u00a0everything to the commit because this will often lead to unwanted changes to be committed and your code will fail CR (code review).
\ngit add .<\/del><\/p><\/blockquote>\nWhen you\u2019re done, push the branch on the upstream repo so others can access it:<\/p>\n
git push upstream [branch name]<\/pre>\nAfter this, create a pull request<\/strong> from this new branch to the upstream release branch and send the story to QA and CR (together with the pull request url).<\/p>\n <\/p>\n
If everything is ok, the code will be merged into the release branch to test it together with other changes made by you or colleagues developers when working on different stories. When everything is ready to be deployed, the release branch (the upstream release<\/strong>) will be merged into the master and the code will end up on the production server.<\/p>\n <\/p>\n
Congratulations! Now that you know how to use Git, take a break and have a laugh at\u00a0those who don’t:<\/p>\n
<\/p>\n