...
Quick Summary: Developers fork the team repository on Bitbucket. When working on a bug fix or new feature, they create a topic branch specific to that task. They push their branch to their fork for review and testing. When all is done, they submit a pull request from the topic branch on their fork to the master branch on the team repository. When working on a task recorded in the IGB JIRA system, they include the corresponding JIRA number (e.g., IGBF-1234) in the branch name and every commit to that branch.
| Table of Contents |
|---|
...
Step-by-Step Set-up Guide
...
where IGBF-1234 is the name of the new branch.
Edit code, commit to your clone, push to your fork
Edit your code, test it, commit your edits to your local copy, and then push them to your fork hosted on Bitbucket. If working on a JIRA issue, always include the JIRA ticket name in the commit.
...
| Code Block |
|---|
git push origin IGBF-1234 |
Make a pull request - PR
To request that your edits be incorporated into the team repository, you need to make a pull request (PR).
...