Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Cleaned up the instructions.

...

The following are developer housekeeping responsibilities

...

.   Any code contributions, like creating local QA tests on your local branch

...

, will require a code review

...

before

...

being merged into the scheduledb branch.

  1. Update your local scheduledb branch with the latest remote branch changes.
    git checkout -f scheduledb

...

  1. git pull

...

  1. Create and checkout a new local branch for your work.

...

  1. git checkout -b

...

  1. yourLocalBranchName

...

  1. Create your code changes (e.g. Geb and Spock tests

...

4. Lets be sure we are still working with the latest version of Scheduledb
  # git pull

...

  1. ) into the new local branch.
  2. Commit your changes into your local branch
    git commit -m "describe your code changes"
  3. Get the latest remote branch changes into your local scheduledb branch
    git checkout scheduledb
    git pull
  1. Merge scheduledb to your local branch.
    git checkout yourLocalBranchName

...

  1. git merge scheduledb
6. Create your remote branch for Peer Code Review
  # git push origin yourlocalbranchname
7. Code Review

...

  1. Resolve any merge conflicts.
  2. Push yourLocalBranchName to the remote repository so that the team can evaluate your changes.
    git push origin yourLocalBranchName
  3. Team does a Code Review of your changes
    git checkout scheduledb
    git diff yourLocalBranchName
  4. Once the request is approved by the team, merge yourLocalBranchName into scheduledb.
    git merge -m "Merging yourLocalBranchName into scheduledb" yourLocalBranchName
  5. Push the local scheduledb code changes to the remote branch
    git push