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

When merge commit is used as the merge strategy, the Bamboo build status is not displayed on the PR

    XMLWordPrintable

Details

    • 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

      The Bamboo build status is not shown on the PR if the merge strategy used is no-ff. The build status will go correctly against the merge commit however there is no link from the merge commit to the parent commits in the PR.

      This behavior is different for other merge strategies:

      Fast forward (from command-line): The commit shows up as part of the PR and hence so does the build status.

      Squash (from UI): The squashed commit shows up in the PR with the build status.

      Since the merge commit is not technically considered part of the PR, this behavior appears to be working as intended however some users would still like to see the build status displayed on the PR. Perhaps in the event of a merge commit, we can link the build status back to the parent commit or have a separate display of the build status for any resulting merge commits of a PR, on the PR.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jowen@atlassian.com Jeremy Owen
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: