git permissions force-push:true incorrectly implies create:true
Bug #1815221 reported by
Andy Whitcroft
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| turnip |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
A grant record which grants force-push:true implies a grant of create:true. The effect of this is we cannot specify allowing force-push of existing branches while preventing creation of new. It is possible to specify push to a branch without creation of new.
We (attempted) to use this form to allow force push to branches *-next without considering the actual names.
Related branches
~cjwatson/turnip:force-push-does-not-imply-create
- William Grant: Approve (code)
- Jonathan Hartley (community): Approve
-
Diff: 39 lines (+6/-7)2 files modifiedturnip/pack/hooks/hook.py (+4/-4)
turnip/pack/tests/test_hooks.py (+2/-3)
| Changed in turnip: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in turnip: | |
| assignee: | nobody → Colin Watson (cjwatson) |
| Changed in turnip: | |
| status: | Triaged → In Progress |
| Changed in turnip: | |
| status: | In Progress → Fix Committed |
| Changed in turnip: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
