Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4209

Disable force-push per branch, branch type or branch pattern

XMLWordPrintable

    • 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 our Implementation of New Features Policy.

      As a repository admin I can restrict force-pushes in a more fine-grained manner by specifying which branches do or do not allow force-pushes.

      This would allow for legitimate force-pushes in a feature branch while protecting the default branch.

      Additional acceptance criteria:

      • full regular expression syntax can be used to select branches

          Form Name

            [BSERV-4209] Disable force-push per branch, branch type or branch pattern

            Roger Barnes (Inactive) added a comment -

            Hi ashish.yadav,

            As plans are subject to change, we do not publish roadmaps nor ETAs for feature requests. I'll endeavour to provide a status update on this one in the next few months. If you would like to know more about how Atlassian Product Management uses customer input during the planning process, please see this post on Atlassian Answers and our new features policy.

            Thanks for your patience and we hope you appreciate our open approach to feature requests.

            Roger Barnes (Inactive) added a comment - Hi ashish.yadav , As plans are subject to change, we do not publish roadmaps nor ETAs for feature requests. I'll endeavour to provide a status update on this one in the next few months. If you would like to know more about how Atlassian Product Management uses customer input during the planning process, please see this post on Atlassian Answers and our new features policy . Thanks for your patience and we hope you appreciate our open approach to feature requests.

            Ashish Yadav added a comment -

            This ticket was opened on 12/Dec/13. Doesn't look like it will be implemented anytime soon. Could you please provide an ETA on when these will be resolved. We are waiting for these 'critical' updates for a very long time. Thanks.

            Ashish Yadav added a comment - This ticket was opened on 12/Dec/13. Doesn't look like it will be implemented anytime soon. Could you please provide an ETA on when these will be resolved. We are waiting for these 'critical' updates for a very long time. Thanks.

            Carolyn Van Slyck added a comment -

            I wrote a plugin, Force Field for Stash, which allows you to specify a list of branches to be protected from forced pushes.

            For example: "master release/**" would protect master and all branches which start with release, such as release/v1/1.0, release/v2/2.1, etc.

            The plugin is free and open source, if you would like to contribute, the project is hosted at https://bitbucket.org/carolynvs/stash-force-field.

            Carolyn Van Slyck added a comment - I wrote a plugin, Force Field for Stash , which allows you to specify a list of branches to be protected from forced pushes. For example: "master release/**" would protect master and all branches which start with release, such as release/v1/1.0, release/v2/2.1, etc. The plugin is free and open source, if you would like to contribute, the project is hosted at https://bitbucket.org/carolynvs/stash-force-field .

              Unassigned Unassigned
              b54b3051-02a3-482c-adb4-1125ccb7a257 Deleted Account (Inactive)
              Votes:
              22 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: