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

Allow no-merges policy

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 want to ensure that a branch is not only fast-forward only but also does not contain merges, which enforces committers to this branch to rebase their work properly.

      This helps to keep the commit history sane and reliable to work with using external automation tools. Otherwise, the possibility exists that existing changes are missed out by i.e. reporting tools that evaluate changes between two commits.

      Additional acceptance criteria:

      • The branch name(s) to which this applies can be specified using standard regular expressions


      This request shall enable the same functionality that is available in gitolite:

            Unassigned Unassigned
            5d91f8e59700 Ancoron Luciferis
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: