I have a project repository on a bitbucket server behind a proxy. I am the administrator for the repository in concern. The ask was to freeze a particular release branch (say, release/1.0) and create a new release branch (say, release/2.0) branching out of release/1.0.
Is there a way I can prevent the developers from creating a pull request for merging their feature changes to release/1.0? Instead, they should be creating pull requests to merge their changes only to release/2.0.
Like in the pull request creation page, the target branch dropdown should not show the value - release/1.0. But it should show release/2.0.
I will be grateful and greatly appreciate for any leads regarding this problem
Note: I have also raised a JIRA ticket as a suggestion to address this situation.
I found a ticket in the BitBucket Public IssueTracker titled Add ability to disable pull requests (BB-7143) that was closed as wontfix in 2013 but people are still commenting on the ticket.
I did not see a ticket in JAC. You could create a JAC ticket and link the ticket here and in the BitBucket Public Issue Tracker so the Community can vote on the issue.
@Branden McElveen As suggested by you, I raised a JIRA ticket as a suggestion and added the JIRA ticket link in the description of this thread question. You were talking about a Bitbucket public issue tracker too, how do I get there? Or just adding the JIRA link here in the description would suffice?
I’m Jess, a Product Marketer for Jira Software Server and Data Center, and now a huge fan of our products. Read on for a 90 day, new-hire perspective on what it’s like to standardize on the Atlassian...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs