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

Update dependent PR destinations when merging and closing a PR that is a target

    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

      Right now, a regular part of my team's work flow is to break a feature into a couple Pull Requests in order to keep requests manageable.

      An example:

      • Branch develop into FEAT-123_BasicImpl and set up a Pull Request
      • Branch FEAT-123_BasicImpl into FEAT-124_Extend123 with another Pull Request
      • Merge FEAT-123_BasicImpl when ready
      • Go manually update FEAT-124_Extend123 to point at develop
      • Merge FEAT-124_Extend123 when ready

      Because often different developers are on FEAT-123 and FEAT-124, the manual update step is often forgotten causing broken pull requests.

      My request is that when a Pull Request is merged and if it is set to delete the branch, then any existing Pull Requests which reference the branch to be closed get updated to point at whichever branch it was merged into.

      Attachments

        Activity

          People

            Unassigned Unassigned
            72dc6999a182 CriasSK
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: