Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Why Default Task are not applicable to release branch (Destination)?

Screenshot from 2022-12-08 19-23-51.png


1 answer

0 votes
Michael Rüegg _Mibex Software_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Dec 08, 2022

If you do not mind a separate app, you can create specific tasks for different branch types (including release branches) 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.

For more information, please check the app documentation.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events