Open igor-sirotin opened 1 month ago
cc @siddarthkay do you think it's possible to implement?
Seems doable. I'll take a stab at this.
ouch
A merge queue cannot be enabled with branch protection rules that use wildcard characters (*) in the branch name pattern.
Hmm. Can we make the merge queue at least for develop
for now?
Or does it require to remove branch protection wildcard rules at all?
cc @siddarthkay
currently testing this on a small repo, I'll get back to you with more info.
Problem
Recently we merged #5596 with
Squash and Merge
feature. It formed this f05b7e793dfd500d72ca92d08e1ab5e7ee5576ed with message:And now all PR's on top of it are not passing the commit message check:
https://ci.status.im/blue/organizations/jenkins/status-go%2Fprs%2Ftests/detail/PR-5608/2/pipeline/
Solution
We need to ensure that suqash/merge commits also have proper message. I believe merging queue should help us with this. No need to run the whole CI, just the commit message check.
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue