User Tools

Site Tools


submitting_to_gerrit

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
submitting_to_gerrit [2017/12/08 16:25]
Mats Wichmann
submitting_to_gerrit [2019/10/08 22:32] (current)
George Nash New version of gerrit no longer allows draft commits it now uses private and wip options.
Line 49: Line 49:
   * Once done, push the changeset again to the server, as was done initially<​code bash> $ git push origin HEAD:​refs/​for/<​remote_branch_name>​ </​code>​   * Once done, push the changeset again to the server, as was done initially<​code bash> $ git push origin HEAD:​refs/​for/<​remote_branch_name>​ </​code>​
  
-=== Draft changes ===+=== Private and Work-In-Progress ​changes === 
 + 
 +If you have work that isn't ready for acceptance but something you'd like to have initial reviews on, you can use a Gerrit feature to push private or work-in-progress reviews. The review will be visible only to you and to others you may add as reviewers in the Web UI, rather than to everyone browsing Gerrit. 
 + 
 +To push a private change or to turn a change private on push the ''​private''​ option can be specified:<​code bash> $ git push origin HEAD:​refs/​for/<​remote_branch_name>​%private</​code>​ 
 + 
 +Omitting the ''​private''​ option when pushing updates to a private change doesn’t make change non-private again. To remove the private flag from a change on push, explicitly specify the ''​remove-private''​ option:<​code bash> $ git push origin HEAD:​refs/​for/<​remote_branch_name>​%remove-private</​code>​ 
 + 
 +To push a ''​wip''​ change or to turn a change to ''​wip''​ the work-in-progress (or ''​wip''​) option can be specified:<​code bash> $ git push origin HEAD:​refs/​for/<​remote_branch_name>​%wip</​code>​ 
 + 
 +Omitting the ''​wip''​ option when pushing updates to a ''​wip''​ change doesn’t make change ready again. To remove the ''​wip''​ flag from a change on push, explicitly specify the ''​ready''​ option: <code bash> $ git push origin HEAD:​refs/​for/<​remote_branch_name>​%ready</​code>​
  
-If you have work that isn't ready for acceptance but something you'd like to have initial reviews on, you can use a Gerrit feature to push draft reviews. The review will be visible only to you and to others you may add as reviewers in the Web UI, rather than to everyone browsing Gerrit. 
  
-The procedure is the same as above for both the initial push as well as for updating. The only difference is that you should push to ''​refs/​drafts/<​remote_branch_name>''​ instead of ''​refs/​for/<​remote_branch_name>''​ 
  
submitting_to_gerrit.1512750317.txt.gz · Last modified: 2017/12/08 16:25 by Mats Wichmann