Clarification of Pre-Commit Workflow

I've been reading the workflow page here: https://www.reviewboard.org/docs/manual/2.0/users/getting-started/workflow/ We're planning to follow the pre-commit workflow. Would be grateful if someone could clarify some of the steps for us. Here's my current understanding of the first few steps:

Re: Clarification of Pre-Commit Workflow

won’t need to choose any reviewers. Christian -- Christian Hammond - chri...@beanbaginc.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On August 5, 2014 at 10:42:45 PM, Kevan Stannard (kevans...@gmail.com javascript:) wrote: I've been

Re: Clarification of Pre-Commit Workflow

, TRACKING_BRANCH is set to origin/master. -David On Thu, Aug 7, 2014 at 5:44 PM, Kevan Stannard kevans...@gmail.com javascript: wrote: Many thanks Christian. If we're working in our own branch then what value should we use for TRACKING_BRANCH in .reviewboardrc? At the moment we've committed

How to keep Review Board Git repository up to date?

We are using Review Board with Git. Review Board has it's own local clone of the repository. I'm not sure exactly what our problem is but is seems have something to do with Review Board repository not being in sync with origin. * When we use *rbt post* we occasionally get an error indicating

Re: How to keep Review Board Git repository up to date?

13, 2014 at 11:16:37 PM, Kevan Stannard (kevans...@gmail.com javascript:) wrote: We are using Review Board with Git. Review Board has it's own local clone of the repository. I'm not sure exactly what our problem is but is seems have something to do with Review Board repository not being