Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

Workspace configurations

Joao Pedro Correia
Joao Pedro Correia Oct 24, 2023

can you configure the pipeline in a workspace of all the child repositories that inherit this bitbucket pipeline?

Answer
Watch
Like Be the first to like this
122 views

2 answers

Reply
0 votes
Saxea _Flowie_
Saxea _Flowie_
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.
Get recognized
Oct 24, 2023

Hi @Joao Pedro Correia ,

Not via inheritance, but there're Share Pipelines.

View More Comments
Joao Pedro Correia
Joao Pedro Correia Oct 25, 2023

And branch settings, such as PR activation, merge blocking and direct commits in dev, always making a squash commit, is there any way to make this setting defaut?

Like
Saxea _Flowie_
Saxea _Flowie_
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.
Get recognized
Oct 25, 2023

You can define branch restrictions at Project level, but not at Workspace level, and they are inherited by the repositories. Branch restrictions support merge checks/blocking and direct commits in dev. 

I'm not sure what you mean by PR activation, but you can define PR permissions in branch restrictions as well.

Default merge strategy e.g. squash commit is also supported at Project level for the repositories to inherit it. However you can't enforce it or restrict it.

Flowie, a Bitbucket addon we develop, provides more granular control over these and other settings. e.g. It can enforce a merge strategy per branch for all repositories, defined at Workspace level. Additionally, you could also define that it should always close the branch after a merge for instance.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events

See all events