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

Allow forks to sync with a branch other than the upstream's main branch (BB-10157)

    • 10
    • 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.

      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.

            [BCLOUD-8994] Allow forks to sync with a branch other than the upstream's main branch (BB-10157)

            Dylan added a comment -
            Atlassian Update - May 14, 2025

            Hi everyone,

            Thank you for bringing this Suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap.

            In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management

            Dylan added a comment - Atlassian Update - May 14, 2025 Hi everyone, Thank you for bringing this Suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this Suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. If you’re interested in what’s planned or coming soon, check out our Cloud Roadmap . In addition, if you feel like this Suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products - Atlassian Cloud Product Management

            Attachment 238490258-Screen%20Shot%202014-02-20%20at%2011.08.04%20AM.png has been added with description: Originally embedded in Bitbucket issue #8994 in site/master

            moo (Inactive) added a comment - Attachment 238490258-Screen%20Shot%202014-02-20%20at%2011.08.04%20AM.png has been added with description: Originally embedded in Bitbucket issue #8994 in site/master

            This issue has been closed due to inactivity. If you continue to see problems, please reopen or create a new issue.

            Legacy Bitbucket Cloud User (Inactive) added a comment - This issue has been closed due to inactivity. If you continue to see problems, please reopen or create a new issue.

            @mbrodala,

            Thanks for the clarification. I missed that part of your original request. I've added this issue to our backlog and we'll update this ticket if and when we begin work on it.

            Thanks,
            Jon

            moo (Inactive) added a comment - @mbrodala, Thanks for the clarification. I missed that part of your original request. I've added this issue to our backlog and we'll update this ticket if and when we begin work on it. Thanks, Jon

            Removing component: repository (automated comment)

            Zachary Davis (Inactive) added a comment - Removing component: repository (automated comment)

            Yeah, I noticed that I have full controll in the Compare tool.

            But the sync feature is rendered pointless if it compares the wrong branch. The same goes for the notification about upstream changes.

            Thus my request.

            Mathias Brodala added a comment - Yeah, I noticed that I have full controll in the Compare tool. But the sync feature is rendered pointless if it compares the wrong branch. The same goes for the notification about upstream changes. Thus my request.

            Hi @mbrodala,

            The sync feature is meant to keep the main branch of your fork up-to-date, as this is the most common use case we see. You can use the compare feature to merge other upstream branches into your fork:

            Hope this helps.

            Thanks,
            Jon

            moo (Inactive) added a comment - Hi @mbrodala, The sync feature is meant to keep the main branch of your fork up-to-date, as this is the most common use case we see. You can use the compare feature to merge other upstream branches into your fork: Hope this helps. Thanks, Jon

              Unassigned Unassigned
              113c40534f21 Mathias Brodala
              Votes:
              7 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: