[BCLOUD-8994] Allow forks to sync with a branch other than the upstream's main branch (BB-10157) - Create and track feature requests for Atlassian products.

XML

Word

Printable

Details

Type: Suggestion
Status: Gathering Interest (View Workflow)
Resolution: Unresolved
Component/s: Pull Request - Merge / Checks, Repository - Pull requests
Labels:
- migrated

Feedback Policy:

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

While you can fork a repository and choose a different main branch, there is no way to specify the upstream branch to use for notification and syncing. Bitbucket currently only allows merging the "master" branch into the main branch of your fork, no selection of other branches to merge.

Thus the suggestion: add an option to the Repository details which allows selecting an upstream branch to track and use for notification/sync.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

238490258-Screen%20Shot%202014-02-20%20at%2011.08.04%20AM.png
15 kB
08/Sep/2019 11:38 PM

Activity

People

Assignee:: Unassigned

Reporter:: Mathias Brodala

Votes:: 7 Vote for this issue

Watchers:: 10 Start watching this issue

Dates

Created:: 19/Feb/2014 10:34 AM

Updated:: 21/Oct/2022 8:26 AM