Workspace configurations

[Joao Pedro Correia]

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

[Joao Pedro Correia]

ok thankyou

[Saxea _Flowie_]

Hi @Joao Pedro Correia ,

Not via inheritance, but there're Share Pipelines.

[Joao Pedro Correia]

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?

[Saxea _Flowie_]

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.