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

As an administrator I want to define a non-overridable merge strategy for pull requests

    XMLWordPrintable

Details

    • Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • None
    • None
    • 2
    • 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.

    Description

      Problem Definition

      While it is currently possible in Bitbucket Server to globally define merge strategies for pull requests, this setting can be overridden on a per-repository basis. Depending on the strategy used during merge, information may be lost (by removing commits rather than creating a merge commit) that links commits to JIRA issues, pull requests, etc, which is critical information to maintain for audit purposes.

      Suggested Solution

      There should be a way for an administrator to define a non-overridable merge strategy to be applied to all repositories.

      Workaround

      Don't give anyone repository admin permissions. That way, only the project admin can modify these settings.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              cglockner Christian Glockner
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: