| Issue 2179: | Separate Delete Permission | |
| 6 people starred this issue and may be notified of changes. | Back to list |
I'd like it to be possible to assign a delete permission to a reference that is independent of the "Force Push" permission so that users are able to delete remote branches without being able to interfere with the history of them. I'd much rather someone just deleted a branch (which could be pushed back by someone else if done in error) than force pushed a change which could cause even more problems.
Oct 10, 2013
#1
nickdgri...@gmail.com
Feb 27, 2014
To my mind this is a very good suggestion. It would also make sense, imho, to define some sort of "force" that allows certain (and only certain) users to delete branches that hasn't been integrated yet.
Jan 27, 2015
I'm missing this feature too. Our setup is, that developers have access to create "feature/*" branches, but only push commits to "refs/for/feature/*", i.e. with review, as "feature/*" branches are allowed to be merged to "master" since they by convention in our setup have already been reviewed. But, a developer should also be able to abandon a "feature" branch entirely, either dropping the feature or starting a brand new implementation of it. And since I do not want to give developers force push access rights to "feature/*" to enable them to delete "feature" branches, because they can then also push directly to "refs/heads/feature/*" thus bypassing review, I would like a separate branch delete permission. As it is setup now for us, then whenever a "feature" branch is done, and thus merged to "master", or abandoned by the developer, then an integrator/admin needs to periodically delete old obsolete "feature" branches. |
|
| ► Sign in to add a comment |