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
F18104129: D7406.id16693.diff
Aug 10 2025, 10:05 AM
F18099537: D7406.id.diff
Aug 9 2025, 6:01 AM
F18096770: D7406.diff
Aug 8 2025, 9:06 AM
F17921517: D7406.id16693.diff
Jul 30 2025, 5:27 AM
F17852822: D7406.diff
Jul 27 2025, 1:06 PM
Unknown Object (File)
Jun 2 2025, 8:12 AM
Unknown Object (File)
Jun 2 2025, 2:37 AM
Unknown Object (File)
Jun 2 2025, 2:37 AM
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

Lint
Lint Skipped
Unit
Tests Skipped

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.)