Support GitHub Merge Queue

[wrslatz]

GitHub announced a new merge queue capability that is currently in limited beta. It allows an additional flow path for merging pull requests by adding them to a merge queue (handled by GitHub Actions behind the scenes). This feature is still relatively undocumented, so we can't take action on this yet, but adding this feature to Bulldozer would help Bulldozer integrate well with this new functionality from GitHub.

Additional resources:

• Docs on using a merge queue and adding a pull request to the merge queue
• GraphQL API for enabling the merge queue for a PR
• Option to automatically enable auto-merge for all new PRs community/community#8306, where GitHub says they currently do not plan to automate adding a PR to the merge queue at the platform level

Next steps before implementation could be planned:

• Review API documentation around auto-merge
• Track the corresponding GitHub roadmap issues for full merge queue support (Pull Request Merge Queue github/roadmap#370, Pull Request Merge Queue (GHES) github/roadmap#455)
• Consider implementation
  • This seems separate from the existing merge methods

Additional features to consider once this one is implemented:

• Matching to move to merge queue (trigger, ignore, labels, etc.)
• Matching to jump ahead of the merge queue (trigger, ignore, labels, etc.)

[asvoboda]

Hey @wrslatz,

Thanks for filing this. I think the idea of integrating with the merge queue makes a lot of sense. I think we'll want to wait until the feature is out of public beta to let the API stabilize.

On your points of discussion:

• Should this feature be implemented as a new merge-method, or a separate construct? We may want a separate option, since the merge queue takes as input a merge method and pull request to perform the merge itself.

[wrslatz]

Looks like the merge queue is now exposed via API in this latest update! One step closer to GA and adding support for this feature

[wrslatz]

palantir/policy-bot#554 might be good as reference