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 |
Posting Options: |
9 |
Controls the behavior of a post, including what review request gets |
10 |
posted and how, and what happens after it is posted. |
11 |
|
12 |
-r ID, --review-request-id=ID |
13 |
Specifies the existing review request ID to update. |
14 |
-u, --update Automatically determines the existing review request |
15 |
to update. |
16 |
-p, --publish Immediately publishes the review request after |
17 |
posting. |
18 |
-o, --open Opens a web browser to the review request after |
19 |
posting. |
20 |
--submit-as=USERNAME |
21 |
The user name to use as the author of the review |
22 |
request, instead of the logged in user. |
23 |
--change-only Updates fields from the change description, but does |
24 |
not upload a new diff (Perforce/Plastic only). |
25 |
--diff-only Uploads a new diff, but does not update fields from |
26 |
the change description (Perforce/Plastic only). |
27 |
|
28 |
Review Board Server Options: |
29 |
Options necessary to communicate and authenticate with a Review Board |
30 |
server. |
31 |
|
32 |
--server=SERVER Specifies the Review Board server to use. |
33 |
--disable-proxy Prevents requests from going through a proxy server. |
34 |
--username=USERNAME |
35 |
The user name to be supplied to the Review Board |
36 |
server. |
37 |
--password=PASSWORD |
38 |
The password to be supplied to the Review Board |
39 |
server. |
40 |
|
41 |
Repository Options: |
42 |
--repository=REPOSITORY_NAME |
43 |
The name of the repository configured on Review Board |
44 |
that matches the local repository. |
45 |
--repository-url=REPOSITORY_URL |
46 |
The URL for a repository, used for creating a diff |
47 |
outside of a working copy (currently only supported by |
48 |
Subversion with specific revisions or --diff-filename |
49 |
and ClearCase with relative paths outside the view). |
50 |
For git, this specifies the origin url of the current |
51 |
repository, overriding the origin URL supplied by the |
52 |
git client. |
53 |
--repository-type=REPOSITORY_TYPE |
54 |
The type of repository in the current directory. In |
55 |
most cases this should be detected automatically, but |
56 |
some directory structures containing multiple |
57 |
repositories require this option to select the proper |
58 |
type. The `rbt list-repo-types` command can be used to |
59 |
list the supported values. |
60 |
|
61 |
Review Request Field Options: |
62 |
Options for setting the contents of fields in the review request. |
63 |
|
64 |
-g, --guess-fields Short-hand for --guess-summary --guess-description. |
65 |
--guess-summary Generates the Summary field based on the commit |
66 |
messages (Bazaar/Git/Mercurial only). |
67 |
--guess-description |
68 |
Generates the Description field based on the commit |
69 |
messages (Bazaar/Git/Mercurial only). |
70 |
--change-description=CHANGE_DESCRIPTION |
71 |
A description of what changed in this update of the |
72 |
review request. This is ignored for new review |
73 |
requests. |
74 |
--summary=SUMMARY The new contents for the Summary field. |
75 |
--description=DESCRIPTION |
76 |
The new contents for the Description field. |
77 |
--description-file=FILENAME |
78 |
A text file containing the new contents for the |
79 |
Description field. |
80 |
--testing-done=TESTING_DONE |
81 |
The new contents for the Testing Done field. |
82 |
--testing-done-file=FILENAME |
83 |
A text file containing the new contents for the |
84 |
Testing Done field. |
85 |
--branch=BRANCH The branch the change will be committed on. |
86 |
--bugs-closed=BUGS_CLOSED |
87 |
The comma-separated list of bug IDs closed. |
88 |
--target-groups=TARGET_GROUPS |
89 |
The names of the groups that should perform the |
90 |
review. |
91 |
--target-people=TARGET_PEOPLE |
92 |
The usernames of the people who should perform the |
93 |
review. |
94 |
--markdown Specifies if the summary and description should be |
95 |
interpreted as Markdown-formatted text (Review Board |
96 |
2.0+ only). |
97 |
|
98 |
Diff Generation Options: |
99 |
Options for choosing what gets included in a diff, and how the diff is |
100 |
generated. |
101 |
|
102 |
--revision-range=REVISION_RANGE |
103 |
Generates a diff for the given revision range. |
104 |
[DEPRECATED] |
105 |
-I INCLUDE_FILES, --include=INCLUDE_FILES |
106 |
Includes only the given file in the diff. This can be |
107 |
used multiple times to specify multiple files. |
108 |
--parent=BRANCH The parent branch this diff should be generated |
109 |
against (Bazaar/Git/Mercurial only). |
110 |
--diff-filename=FILENAME |
111 |
Uploads an existing diff file, instead of generating a |
112 |
new diff. |
113 |
|
114 |
Git Options: |
115 |
Git-specific options for selecting revisions for diff generation. |
116 |
|
117 |
--tracking-branch=BRANCH |
118 |
The remote tracking branch from which your local |
119 |
branch is derived (defaults to origin/master). |
120 |
|
121 |
Perforce Options: |
122 |
Perforce-specific options for selecting the Perforce client and |
123 |
communicating with the repository. |
124 |
|
125 |
--p4-client=CLIENT_NAME |
126 |
The Perforce client name for the repository. |
127 |
--p4-port=PORT The IP address for the Perforce server. |
128 |
--p4-passwd=PASSWORD |
129 |
The Perforce password or ticket of the user in the |
130 |
P4USER environment variable. |
131 |
|
132 |
Subversion Options: |
133 |
Subversion-specific options for controlling diff generation. |
134 |
|
135 |
--basedir=PATH The path within the repository where the diff was |
136 |
generated. This overrides the detected path. Often |
137 |
used when passing --diff-filename. |
138 |
--svn-show-copies-as-adds=y/n |
139 |
Treat copied or moved files as new files. |
140 |
--svn-changelist=ID |
141 |
Generates the diff for review based on a local |
142 |
changelist. [DEPRECATED] |