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

Proactively show downstream merge conflicts on Bitbucket UI

    XMLWordPrintable

    Details

    • UIS:
      5
    • Feedback Policy:
      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

      Suppose I have a branch intended for rel/<foo> that will also need to be forwarded to a master-aligned train. Bitbucket will warn me if a parallel change to the project by some other engineer has introduced a merge conflict on my branch, which lets me fix it proactively. That’s great.

      But if the merge conflict won’t happen until my diff is forward to master, nothing in the current Bitbucket UI will show me that fact.

      I could imagine a Bitbucket enhancement to proactively detect and flag the guaranteed downstream merge failures, which would let me fix the problem as early in the workflow as possible.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            corey26 Corey Steele
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but there is no synchronization info for this issue.