Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-2586

Add user permission for allowing/denying non fast forward pushes

    Details

      Description

      Related to STASH-2507. There's a comment on that bug noting that there should be an accompanying permission for push rewind and I felt it deserved a separate request.

      At my company we create many short-lived branches, so deleting them is common, but we rarely want people to do a rewind.

        Attachments

          Issue Links

            Activity

            Hide
            ssaasen Stefan Saasen added a comment -

            Vince Rosso, Mikko Hyvärinen thanks for the clarification. The Bitbucket settings attached are in fact on a repository level as this maps directly to the respective settings in git (which are applied on a per repository level).

            STASH-2521 covers adding custom commit hooks that could enforce more fine grained permission schemes.

            Show
            ssaasen Stefan Saasen added a comment - Vince Rosso , Mikko Hyvärinen thanks for the clarification. The Bitbucket settings attached are in fact on a repository level as this maps directly to the respective settings in git (which are applied on a per repository level). STASH-2521 covers adding custom commit hooks that could enforce more fine grained permission schemes.
            Hide
            llvince Vince Rosso added a comment -

            Yes, this could be handled in git hooks (as probably many other requests could be) but then how would you manage permissions? This should be built into and managed in Stash. It already has a limited permission model, it needs to be expanded to handle more complex use cases.

            Show
            llvince Vince Rosso added a comment - Yes, this could be handled in git hooks (as probably many other requests could be) but then how would you manage permissions? This should be built into and managed in Stash. It already has a limited permission model, it needs to be expanded to handle more complex use cases.
            Hide
            mhyvarin Mikko Hyvärinen added a comment -

            I fully agree with Vince.

            Show
            mhyvarin Mikko Hyvärinen added a comment - I fully agree with Vince.
            Hide
            llvince Vince Rosso added a comment -

            I've updated the title to make it clear that this is a request for a user level permission, not a repository setting.

            Show
            llvince Vince Rosso added a comment - I've updated the title to make it clear that this is a request for a user level permission, not a repository setting.
            Hide
            jens@atlassian.com Jens Schumacher added a comment -

            This has been resolved as part of http://blogs.atlassian.com/2013/03/stash-22-customize-workflow-git-hooks-api-merge-checks.

            Please let us know if the hook does not meet all your requirements.

            Show
            jens@atlassian.com Jens Schumacher added a comment - This has been resolved as part of http://blogs.atlassian.com/2013/03/stash-22-customize-workflow-git-hooks-api-merge-checks . Please let us know if the hook does not meet all your requirements.

              People

              • Assignee:
                Unassigned
                Reporter:
                llvince Vince Rosso
              • Votes:
                24 Vote for this issue
                Watchers:
                24 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: