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

Default merge branch for PR should be the immediate parent branch (or maybe an option to merge into the default)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 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.

      When I create a branch from a ticket in JIRA it gives me the option to choose what branch to base the new branch off of. We follow the workflow where normally you're branching from a branch and then merging back into that branch. This applies even for cherry picks where you're moving from one master branch to another (or from master to a release branch or something like that.)

      In any case, since I've already specified where the branch should originate; and the typical workflow is to merge back into that branch, it's unexpected that bamboo / bitbucket would choose to create the PR to go back into the default branch.

      My suggestion is to have the PR by default merge back into its immediate parent; and maybe, if that differs from the default branch to put a ! warning, or a model dialog asking if that's what you want to do.

              Unassigned Unassigned
              f4787cf404c1 Matt Walker
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: