Usage: rbt post [options] [revisions] Uploads diffs to create and update review requests. Options: -d, --debug display debug output Review Board Server Options: Options necessary to communicate and authenticate with a Review Board server. --server=SERVER specify a different Review Board server to use --disable-proxy prevents requests from going through a proxy server --username=USERNAME user name to be supplied to the Review Board server --password=PASSWORD password to be supplied to the Review Board server Repository Options: --repository=REPOSITORY_NAME the name of the repository configured on Review Board that matches the local repository --repository-url=REPOSITORY_URL the url for a repository for creating a diff outside of a working copy (currently only supported by Subversion with specific revisions or --diff-filename and ClearCase with relative paths outside the view). For git, this specifiesthe origin url of the current repository, overriding the origin url supplied by the git client. --repository-type=REPOSITORY_TYPE the type of repository in the current directory. In most cases this should be detected automatically, but some directory structures containing multiple repositories require this option to select the proper type. The `rbt list-repo-types` command can be used to list the supported values. Posting Options: Controls the behavior of a post, including what review request gets posted and how, and what happens after it is posted. -r ID, --review-request-id=ID existing review request ID to update -u, --update automatically determine the existing review request to update -p, --publish publish the review request immediately after submitting -o, --open open a web browser to the review request page --submit-as=USERNAME user name to be recorded as the author of the review request, instead of the logged in user --change-only updates info from changelist, but does not upload a new diff (only available if your repository supports changesets) --diff-only uploads a new diff, but does not update info from the changelist. Review Request Field Options: Options for setting the contents of fields in the review request. -g, --guess-fields equivalent to --guess-summary --guess-description --guess-summary guess summary from the latest commit (bzr/git/hg/hgsubversion only) --guess-description guess description based on commits on this branch (bzr/git/hg/hgsubversion only) --change-description=CHANGE_DESCRIPTION description of what changed in this revision of the review request when updating an existing request --summary=SUMMARY summary of the review --description=DESCRIPTION description of the review --description-file=FILENAME text file containing a description of the review --testing-done=TESTING_DONE details of testing done --testing-done-file=FILENAME text file containing details of testing done --branch=BRANCH affected branch --bugs-closed=BUGS_CLOSED list of bugs closed --target-groups=TARGET_GROUPS names of the groups who will perform the review --target-people=TARGET_PEOPLE names of the people who will perform the review --markdown whether the summary and description should be interpreted as Markdown-formatted text (Review Board 2.0+ only) Diff Generation Options: Options for choosing what gets included in a diff, and how the diff is generated. --revision-range=REVISION_RANGE generate a diff with the given revision range (DEPRECATED) -I INCLUDE_FILES, --include=INCLUDE_FILES include only the given file in the diff (can be used multiple times) --parent=BRANCH the parent branch this diff should be against (only available if your repository supports parent diffs) --diff-filename=FILENAME upload an existing diff file, instead of generating a new diff Git Options: Git-specific options for selecting revisions for diff generation. --tracking-branch=BRANCH Tracking branch from which your branch is derived (defaults to origin/master) Perforce Options: Perforce-specific options for selecting the Perforce client and communicating with the repository. --p4-client=CLIENT_NAME the Perforce client name that the review is in --p4-port=PORT the Perforce servers IP address that the review is on --p4-passwd=PASSWORD the Perforce password or ticket of the user in the P4USER environment variable Subversion Options: Subversion-specific options for controlling diff generation. --basedir=PATH the absolute path in the repository the diff was generated in. Will override the detected path. --svn-show-copies-as-adds=y/n don't diff copied or moved files with their source --svn-changelist=ID generate the diff for review based on a local SVN changelist