Page MenuHomePhabricator

Improve consistency of policy enforcement on new repository edit UI
ClosedPublic

Authored by epriestley on Oct 25 2013, 9:11 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jun 5, 12:37 AM
Unknown Object (File)
Apr 10 2026, 3:51 PM
Unknown Object (File)
Apr 5 2026, 3:18 AM
Unknown Object (File)
Mar 28 2026, 5:25 PM
Unknown Object (File)
Mar 14 2026, 11:11 AM
Unknown Object (File)
Mar 14 2026, 1:49 AM
Unknown Object (File)
Mar 3 2026, 10:17 PM
Unknown Object (File)
Jan 19 2026, 11:33 PM
Subscribers

Details

Reviewers
btrahan
Maniphest Tasks
Restricted Maniphest Task
Commits
Restricted Diffusion Commit
rPe81bad9ba21f: Improve consistency of policy enforcement on new repository edit UI
Summary

Ref T2231. The policy rules are a little murky right now: the "Edit Repository" link requires CAN_EDIT, but the actualy page doesn't. Instead, require CAN_EDIT for the edit page.

Test Plan

As a user without CAN_EDIT, viewed a repository and clicked the edit link.

Diff Detail

Branch
dedit1
Lint
Lint Passed
Unit
No Test Coverage

Event Timeline

btrahan added inline comments.
src/applications/diffusion/controller/DiffusionRepositoryCreateController.php
28

this should be CAN_EDIT, right? (On that note, I could imagine CAN_CREATE being desired for repositories (and projects))

src/applications/diffusion/controller/DiffusionRepositoryCreateController.php
28

Ack, good catch!

(We have a create policy for projects already and I'll add one for repositories pretty soon.)