Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-15394

Safe merges from certain branches without merge checks

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      We use Git Flow for our branching strategy (http://nvie.com/posts/a-successful-git-branching-model) That basically our branches represent different levels of stability:

      • master branch is the most stable.
      • release-x.y.z is not as stable as master, but more stable than,
      • develop branch which is again more stable than
      • feature-my-awesome-feature branch.

      Having merge checks makes perfect sense when merging from lesser stable to more stable branches, such as merging a feature branch into develop (there the merge checks and pull requests are a way to increase stability).

      However, merging the other way is always considered safe, i.e., it is always safe to merge release-x.y.z branch into develop, since that should not decrease stability of the develop branch since the release branch is more stable.

      With the current implementation of merge checks it is only possible to restrict on the target branch. For example, it means I can only implement rules for the develop branch and those rules are the same if it is a feature branch or a release-x.y.z branches that should be merged.

      I would like to have a method for the developers to easily do the safe merges from stable branches to the lesser stable branches without having to go through pull requests and all of the merge checks.

      Link to the relevant repository: https://bitbucket.org/mirrobots/mir

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            1c4267ac-a67d-44c2-a4f7-61de2e909f9f Deleted Account (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: