Page MenuHomePhabricator

Allow users to "Force accept" package reviews if they own a more general package
ClosedPublic

Authored by epriestley on Mar 28 2017, 4:51 PM.
Tags
None
Referenced Files
F13286133: D17569.id42273.diff
Tue, Jun 4, 6:42 AM
F13284069: D17569.id42266.diff
Sun, Jun 2, 11:28 PM
F13259436: D17569.id42273.diff
Sun, May 26, 8:30 PM
F13256826: D17569.id42273.diff
Sat, May 25, 6:11 PM
F13256801: D17569.id.diff
Sat, May 25, 5:45 PM
F13256270: D17569.id42266.diff
Sat, May 25, 10:49 AM
F13247792: D17569.id42267.diff
Thu, May 23, 10:33 PM
F13226824: D17569.diff
Sun, May 19, 11:35 PM
Subscribers
None

Details

Summary

Ref T12272. If you own a package which owns "/", this allows you to force-accept package reviews for packages which own sub-paths, like "/src/adventure/".

The default UI looks something like this:

[X] Accept as epriestley
[X] Accept as Root Package
[ ] Force accept as Adventure Package

By default, force-accepts are not selected.

(I may do some UI cleanup and/or annotate "because you own X" in the future and/or mark these accepts specially in some way, particularly if this proves confusing along whatever dimension.)

Test Plan

Screen Shot 2017-03-28 at 9.49.22 AM.png (289×747 px, 38 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

  • Fix reject logic so it doesn't auto-force-reject everything you have authority-by-force over.
This revision is now accepted and ready to land.Mar 28 2017, 6:12 PM

me too buddy

I'll think a bit more about how we can, e.g., get test coverage here. All the pieces are kind of unwieldy and inherently interdependent and difficult to split apart. I haven't really come up with anything too promising yet. Maybe easier during/after T10574.

This revision was automatically updated to reflect the committed changes.