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
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
I'm creating a new pull request in Bitbucket and I want to know if there is a way to add Tasks to avoid merging without pre-conditions. After creating the new pull request, I'd like to add specific conditions for reviewers to check the Tasks after they complete the review and if they didn't finish yet, blocks the merge button (waiting for all tasks to be done).
Do you guys have any ideas if is it possible to do in Bitbucket pull requests?
Hi and welcome to the Atlassian Community!
If you do not mind a separate app, you can achieve this with our Checklist Buddy for Bitbucket Cloud.
It uses configuration as code for the definition of the default task rules, which allows reviewing changes by peers, tracking changes over time and all the other benefits Git has over UI-based configurations.
To restrict default tasks for certain branches, you can use this syntax:
--target release/* +task+ Release notes ready?
Besides the configuration of the source/target branch, it is also able to create content-dependent default tasks, e.g.
--files /app/*.jsx +task+ UI changes visually inspected on IE/Edge
creates the default task only if the PR contains any React JSX files.
You can also enforce that all tasks are resolved before merging with the
"No unresolved pull request tasks" merge check in the repository settings.
For more information, please check the app documentation.