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

Pull requests should go back to forked-from repo by default (BB-9378)

    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

      I'm setting up a workflow where each developer has his own fork on Bitbucket. He pushes his changesets there and issue a pull request for someone to review the changesets before merging them back into the main repository.

      It would therefore be helpful if the pull request screen would default to the main repo as the pull request destination. The named branch should also be kept as is: if I make a change on the stable branch in my repo, I want the change to be on the stable branch in the main repo too.

      Generally, I think it makes little sense to issue cross-named branch pull requests with Mercurial. For Git or when using Mercurial bookmarks it makes a lot of sense, but named branches are meant for long-term branches where you don't merge on a per-feature basis.

      Attachments

        Activity

          People

            Unassigned Unassigned
            e07804f3a382 mg
            Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: