Workflow

Relevant link: http://coders-log.blogspot.com/2009/05/creating-remote-branch-with-git.html And another one: http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html

The following are two possibilities for workflow in writing code, getting it reviewed, and checking it into the repository:

1. Remote code review branch and release branch

• Coder writes and finishes code up to his/her own spec in local repository
• Coder checks changes into remote code review branch
• After code review, coder implements bugfixes and suggested changes
• Coder submits second patch to review branch and merges to release branch
• (Another possibility for the above model is to create a remote branch for a new patch every time there's a code to be reviewed. When the patch is edited and finalized, the new patch would be submitted to the release branch and the remote branch would be deleted.)

2. Single remote branch

• Coder writes and finishes code up to his/her own spec in local repository
• Coder submits patch to remote repository
• After code review, coder implements bugfixes and suggested changes
• Coder submits second patch to remote repository