More sophisticated merge checks

[Bence Daday]

Hello,

I would be interested in using the feature mentioned in this ticket:
https://jira.atlassian.com/browse/BCLOUD-20395

As I can see, the comments on the issue also pointed out that the workaround mentioned doesn't cover the request. Could you please re-open the ticket, or is there a solution that could cover this case?

Can we expect to have a solution for a bit more sophisticated logic on merge checks, like what GitHub offers?
Things like selecting which builds / checks would we want to be mandatory, while leaving some as optional, and what's mentioned in the ticket above for letting specific users bypass restrictions.

Best,
Bence

[Syahrul · Accepted solution]

Hi @Bence Daday 

Welcome to the community!

We have Forge, a great tool you can use to create more sophisticated merge checks. I think this might be just what you need, so please take a look at it here:

Bitbucket custom merge check 

Regards,
Syahrul

[Bence Daday]

Hi,

Yes, I have found Forge, it sounds great and that is what we are going to use most likely. But only because we have to.

For what I would consider simple, basic logic which is mentioned on my question here, I think it covers a pretty common and useful case, and I feel like it would make sense to have it as part of the product.
( Especially considering that now we will basically have to implement functionality ourselves that is freely available on GitHub for example. )

That's why I was hoping that with this question, you could also see if more people would be interested in having something similar, and if you deem that it is so, it would be great if you could create a feature request ticket, or re-open the one that I have mentioned above.

Best,
Bence

[Syahrul]

Hi @Bence Daday 

Got it, that makes sense! I've submitted a new feature request since the original one has been closed a few years ago. I'll also share this internally to see if we have any plans for it. To stay updated, be sure to vote and watch the feature request!

• https://jira.atlassian.com/browse/BCLOUD-23774

Regards,
Syahrul

[Bence Daday]

Thank you, although the description is not correct, I meant this being included in Bitbucket, the base product itself. (Forge can already handle this to my knowledge)

[Syahrul]

Hey @Bence Daday 

Got it, updated the feature request description.

Thanks!
Syahrul

[Saxea _Flowie_]

Hi @Bence Daday ,

You might find Flowie useful, it's a paid (note that Forge is also paid) Bitbucket addon we provide, which comes with highly configurable built-in merge checks, that addresses the most common scenarios. If you need more flexibility you can extend it with your own custom logic.

Flowie supports running checks based on conditions, so you can specify checks that only runs based on the files that were changed, or which labels the pull request have, or pretty much any aspect of the PR.

For instance, a typical workflow is to skip some checks for emergency patches. So PRs that are labeled as Priority:Highest don't have to run all the checks. Using this approach, as opposed to overriding checks, has the advantage that you don't need the person who has the permission available just to be able to press merge button. It is also more compliance friendly.

We are also implementing labels permissions which enables you to specify that only users in specific groups can use a label, or label value. So in the scenario above, only users in a specific group would be able to set PR priority as Highest.

We also intend to add support for optional merge checks, so if conditional checks is not enough for your needs, you can get in touch with us on support@flowie.app and let us know. 

[Bence Daday]

Thank you for bringing it to my attention, I'll check it out