opendev
/
gerrit
Code Issues Proposed changes

Docs: Add use-case for Private changes 

Having a controlled pre-review with a controlled sub-set before
opening up for formal review is a sought after feature that is
often requested.
Document the fact that "Private" supports it.

Change-Id: I5d313d3b6132eaeb829a3f19a1ac4f059b2583be
This commit is contained in:
Sven Selberg 2019-01-16 14:59:24 +01:00
parent 47fdfb96e7
commit 038473962e
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/intro-user.txt
View File

@ -565,6 +565,11 @@ click *Start Review*.
Private changes are changes that are only visible to their owners and Private changes are changes that are only visible to their owners and
reviewers. Private changes are useful in a number of cases: reviewers. Private changes are useful in a number of cases:
* You want a set of collaborators to review the change before formal review
starts. By creating a Private change and adding only a selected few as
reviewers you can control who can see the change and get a first opinion
before opening up for all reviewers.
* You want to check what the change looks like before formal review starts. * You want to check what the change looks like before formal review starts.
By marking the change private without reviewers, nobody can By marking the change private without reviewers, nobody can
prematurely comment on your changes. prematurely comment on your changes.