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

Allow merging via pull request but disallow pushing directly to branch



    • Feedback Policy:
      We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see An updated workflow for server feature suggestions.


      Atlassian status as of May 2015

      Hi everyone,

      Thanks for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Stash.

      This suggestion is a priority for the Stash development team and is on our roadmap, however we're not able to provide a timeline for when it will be resolved.

      Product feedback is collected from a number of different sources and is evaluated when planning the product roadmap. You can learn more about our process here.

      Roger Barnes
      Product Manager - Stash

      Original request description:

      Forcing all merges to a certain branch (except for key people) to go via pull requests is currently possible in branch permissions.

      Pull Requests give traceability and the option to comment on code being merged in - in addition, developers can use plugins and merge checks to add additional controls and warnings to the Pull Request page.

      This means that automated checks can be added as merge checks and the people that can be allowed to merge is greater than those who can push - a pre-receive hook doesn't allow good feedback or warnings to the user (as well as not having the context of the branch being merged in, the author etc), so allowing only a restricted set of users to push but allowing all to merge a pull request is desirable.


          Issue Links



              • Assignee:
                mwatson@atlassian.com Matthew Watson
              • Votes:
                252 Vote for this issue
                152 Start watching this issue


                • Created: