1 |
Usage: rbt post [options] [revisions] |
2 |
|
3 |
Uploads diffs to create and update review requests. |
4 |
|
5 |
Options: |
6 |
-d, --debug display debug output |
7 |
|
8 |
Review Board Server Options: |
9 |
Options necessary to communicate and authenticate with a Review Board |
10 |
server. |
11 |
|
12 |
--server=SERVER specify a different Review Board server to use |
13 |
--disable-proxy prevents requests from going through a proxy server |
14 |
--username=USERNAME |
15 |
user name to be supplied to the Review Board server |
16 |
--password=PASSWORD |
17 |
password to be supplied to the Review Board server |
18 |
|
19 |
Repository Options: |
20 |
--repository=REPOSITORY_NAME |
21 |
the name of the repository configured on Review Board |
22 |
that matches the local repository |
23 |
--repository-url=REPOSITORY_URL |
24 |
the url for a repository for creating a diff outside |
25 |
of a working copy (currently only supported by |
26 |
Subversion with specific revisions or --diff-filename |
27 |
and ClearCase with relative paths outside the view). |
28 |
For git, this specifiesthe origin url of the current |
29 |
repository, overriding the origin url supplied by the |
30 |
git client. |
31 |
--repository-type=REPOSITORY_TYPE |
32 |
the type of repository in the current directory. In |
33 |
most cases this should be detected automatically, but |
34 |
some directory structures containing multiple |
35 |
repositories require this option to select the proper |
36 |
type. The `rbt list-repo-types` command can be used to |
37 |
list the supported values. |
38 |
|
39 |
Posting Options: |
40 |
Controls the behavior of a post, including what review request gets |
41 |
posted and how, and what happens after it is posted. |
42 |
|
43 |
-r ID, --review-request-id=ID |
44 |
existing review request ID to update |
45 |
-u, --update automatically determine the existing review request to |
46 |
update |
47 |
-p, --publish publish the review request immediately after |
48 |
submitting |
49 |
-o, --open open a web browser to the review request page |
50 |
--submit-as=USERNAME |
51 |
user name to be recorded as the author of the review |
52 |
request, instead of the logged in user |
53 |
--change-only updates info from changelist, but does not upload a |
54 |
new diff (only available if your repository supports |
55 |
changesets) |
56 |
--diff-only uploads a new diff, but does not update info from the |
57 |
changelist. |
58 |
|
59 |
Review Request Field Options: |
60 |
Options for setting the contents of fields in the review request. |
61 |
|
62 |
-g, --guess-fields equivalent to --guess-summary --guess-description |
63 |
--guess-summary guess summary from the latest commit |
64 |
(bzr/git/hg/hgsubversion only) |
65 |
--guess-description |
66 |
guess description based on commits on this branch |
67 |
(bzr/git/hg/hgsubversion only) |
68 |
--change-description=CHANGE_DESCRIPTION |
69 |
description of what changed in this revision of the |
70 |
review request when updating an existing request |
71 |
--summary=SUMMARY summary of the review |
72 |
--description=DESCRIPTION |
73 |
description of the review |
74 |
--description-file=FILENAME |
75 |
text file containing a description of the review |
76 |
--testing-done=TESTING_DONE |
77 |
details of testing done |
78 |
--testing-done-file=FILENAME |
79 |
text file containing details of testing done |
80 |
--branch=BRANCH affected branch |
81 |
--bugs-closed=BUGS_CLOSED |
82 |
list of bugs closed |
83 |
--target-groups=TARGET_GROUPS |
84 |
names of the groups who will perform the review |
85 |
--target-people=TARGET_PEOPLE |
86 |
names of the people who will perform the review |
87 |
--markdown whether the summary and description should be |
88 |
interpreted as Markdown-formatted text (Review Board |
89 |
2.0+ only) |
90 |
|
91 |
Diff Generation Options: |
92 |
Options for choosing what gets included in a diff, and how the diff is |
93 |
generated. |
94 |
|
95 |
--revision-range=REVISION_RANGE |
96 |
generate a diff with the given revision range |
97 |
(DEPRECATED) |
98 |
-I INCLUDE_FILES, --include=INCLUDE_FILES |
99 |
include only the given file in the diff (can be used |
100 |
multiple times) |
101 |
--parent=BRANCH the parent branch this diff should be against (only |
102 |
available if your repository supports parent diffs) |
103 |
--diff-filename=FILENAME |
104 |
upload an existing diff file, instead of generating a |
105 |
new diff |
106 |
|
107 |
Git Options: |
108 |
Git-specific options for selecting revisions for diff generation. |
109 |
|
110 |
--tracking-branch=BRANCH |
111 |
Tracking branch from which your branch is derived |
112 |
(defaults to origin/master) |
113 |
|
114 |
Perforce Options: |
115 |
Perforce-specific options for selecting the Perforce client and |
116 |
communicating with the repository. |
117 |
|
118 |
--p4-client=CLIENT_NAME |
119 |
the Perforce client name that the review is in |
120 |
--p4-port=PORT the Perforce servers IP address that the review is on |
121 |
--p4-passwd=PASSWORD |
122 |
the Perforce password or ticket of the user in the |
123 |
P4USER environment variable |
124 |
|
125 |
Subversion Options: |
126 |
Subversion-specific options for controlling diff generation. |
127 |
|
128 |
--basedir=PATH the absolute path in the repository the diff was |
129 |
generated in. Will override the detected path. |
130 |
--svn-show-copies-as-adds=y/n |
131 |
don't diff copied or moved files with their source |
132 |
--svn-changelist=ID |
133 |
generate the diff for review based on a local SVN |
134 |
changelist |