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

Make destination repository more obvious when raising PRs from forks

    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

      Scenario

      1. Fork repo A to repo B
      2. Create branch B.foo from B.master
      3. Modify foo and push back into B
      4. Create pull request in B for branch foo

      By default, Bitbucket will set the target of the pull request to A.master. The user can override this.

      However, it's very easy to not notice this and issue a pull request for B.foo -> A.master when it was really intended for B.master.

      Suggestion

      In situations where a pull request is being raised in a fork, make more of a fuss about selecting the correct destination.

      Attachments

        Activity

          People

            Unassigned Unassigned
            c8bca8f00799 ellery-mckenzie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: