Context

"Merge queue takes care of making sure your pull request is compatible with other changes ahead of it and alerting you if something goes wrong."

https://github.blog/news-insights/product-news/github-merge-queue-is-generally-available/

CLOUDP-204508 and DEVPROD-6657 describe similar efforts.

PROS:

• We can prevent the case where a PR is merged ahead of us doesn't cause a merge conflict but does cause a failure
• Forces us to keep a minimum set of tests passing that are gating the merge queue
• We can merge a PR right away once it is approved

CONS:

• If our tests become noisy or have temporary failures, we'll need to be more aggressive in skipping or working around failures so the merge queue remains viable.

Definition of done

Enable merge queue on the master branch and evaluate its usage.

Pitfalls

Described in CONS above.