From 038473962e53640c8b9a713ab1e364b31bf929b0 Mon Sep 17 00:00:00 2001 From: Sven Selberg Date: Wed, 16 Jan 2019 14:59:24 +0100 Subject: [PATCH] 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 --- Documentation/intro-user.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/intro-user.txt b/Documentation/intro-user.txt index d448241423..857e04c918 100644 --- a/Documentation/intro-user.txt +++ b/Documentation/intro-user.txt @@ -565,6 +565,11 @@ click *Start Review*. Private changes are changes that are only visible to their owners and 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. By marking the change private without reviewers, nobody can prematurely comment on your changes.