You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello Team,
I have tried to get more information on Pull Request Please for Bitbucket Server plugin replacement. Reached out to Mibexsoftware, they says this functionality already built-in for newer Bitbucket versions.
Is it true? if so which Bitbucket DC supports this functionality?
So far i understand this plugin provide functionality to protect Git branch and tag references from pushes without a pull request, restriction can be Specific Git refs, Patterns for Git refs & pre-receive hook.
Can anyone provide and suggest, how to reduce the dependency on the third party plugin instead use base Application functionality
Regards
Srikanth
Thank you, I have gone through Article.
Now I'm looking to migrate the plugin data or configure to native application.
I have collected list of repositories using this plugin but migration of this config is another issue. Do you any solution?
Regards
Srikanth
Hi Srikanth,
The app vendor here.
To get the current hook settings, you can use the hook settings REST endpoint.
The hook key is ch.mibex.stash.prp:isPullRequest
For migrating to the Bitbucket branch permissions , I suggest that you use the create ref restriction REST endpoint from Bitbucket.
The corresponding branch restriction type is pull-request-only. You need to pass the list of branches to protect from the hook as "matcher" to this endpoint.
Does that help?
Best regards,
Michael from Mibex