Add "All" and "With Non-Owner Author" options for all Owners Package autoreview rules
Summary: Ref T13099. See PHI424. Fixes T11664. Several installs are interested in having these behaviors available in Owners by default and they aren't difficult to provide, it just makes the UI kind of messy. But I think there's enough general interest to justify it, now. Test Plan: Created a package which owns "/" with a "With Non-Owner Author" review rule which I own. Created a revision, no package reviewer. Changed rule to "All", updated revision, got package reviewer. Maniphest Tasks: T13099, T11664 Differential Revision: https://secure.phabricator.com/D19180
This commit is contained in:
@@ -84,21 +84,26 @@ You can configure **Auto Review** for packages. When a new code review is
|
||||
created in Differential which affects code in a package, the package can
|
||||
automatically be added as a subscriber or reviewer.
|
||||
|
||||
The available settings are:
|
||||
The available settings allow you to take these actions:
|
||||
|
||||
- **No Autoreview**: This package will not be added to new reviews.
|
||||
- **Subscribe to Changes**: This package will be added to reviews as a
|
||||
subscriber. Owners will be notified of changes, but not required to act.
|
||||
- **Review Changes**: This package will be added to reviews as a reviewer.
|
||||
Reviews will appear on the dashboards of package owners.
|
||||
- **Review Changes (Blocking)** This package will be added to reviews
|
||||
as a blocking reviewer. A package owner will be required to accept changes
|
||||
- **Review Changes (Blocking)** This package will be added to reviews as a
|
||||
blocking reviewer. A package owner will be required to accept changes
|
||||
before they may land.
|
||||
- **Subscribe to Changes**: This package will be added to reviews as a
|
||||
subscriber. Owners will be notified of changes, but not required to act.
|
||||
|
||||
NOTE: These rules **do not trigger** if the change author is a package owner.
|
||||
They only apply to changes made by users who aren't already owners.
|
||||
If you select the **With Non-Owner Author** option for these actions, the
|
||||
action will not trigger if the author of the revision is a package owner. This
|
||||
mode may be helpful if you are using Owners mostly to make sure that someone
|
||||
who is qualified is involved in each change to a piece of code.
|
||||
|
||||
These rules also do not trigger if the package has been archived.
|
||||
If you select the **All** option for these actions, the action will always
|
||||
trigger even if the author is a package owner. This mode may be helpful if you
|
||||
are using Owners mostly to suggest reviewers.
|
||||
|
||||
These rules do not trigger if the package has been archived.
|
||||
|
||||
The intent of this feature is to make it easy to configure simple, reasonable
|
||||
behaviors. If you want more tailored or specific triggers, you can write more
|
||||
|
||||
Reference in New Issue
Block a user