Skip to content
Permalink
Browse files
Revised Workflow Steps
  • Loading branch information
aa7401 committed Nov 24, 2019
1 parent 2b18458 commit 3e6c77ac5cc116c2345976773997921140ccd19a
Showing 1 changed file with 6 additions and 3 deletions.
@@ -37,13 +37,16 @@ Start working on the assignment. Remember to install all the dependencies listed

You should not be committing directly to the **master** branch, instead each task or activity you complete should be in its own _feature branch_. You should following the following steps:

1. Log onto GitHub and add an issue to the _issue tracker_, this is your _todo_list.
1. Log onto GitHub and add an issue to the _issue tracker_, this is your _todo_ list.
2. Create a local feature branch making sure that the name of the branch includes both the issue _number_ and _title_ (in lower case).
1. For example: `git checkout -b iss023/fix-login-bug`.
2. You can see a list of all the local branches using `git branch`.
3. When the task is complete and all the tests pass, push the feature branch to GitHub.
3. As you work on the issue make your local commits by:
1. staging the files with `git add --all`.
2. committing with the `no-ff` flag, eg. `git commit --no-ff -m 'detailed commit message here'`.
4. When the task is complete and all the tests pass, push the feature branch to GitHub.
1. For example `git push origin iss023/fix-login-bug` would push the branch named above.
2. Switch back to the _master_ branch with `git checkout master`.
4. Back on GitHub raise a **Pull Request** that merges this feature branch to the _master_ branch.
5. Back on GitHub raise a **Pull Request** that merges this feature branch to the _master_ branch.
5. If there are no issues you can then merge the branch using the button in the _Pull Request_ interface.
6. Pull the latest version of the master branch code using `git pull origin master`.

0 comments on commit 3e6c77a

Please sign in to comment.