GitHub makes its asynchronous pull request merge API generally available
GitHub says its async merge API can merge individual or stacked pull requests, add pull requests to a merge queue, and optionally bypass rules for users with permission. Clients submit merges with PUT and poll status with GET using the returned request ID.
SessionWatcher editorial · Published · Updated · Source announcement: 2026-10-01
What the API supports
GitHub says the generally available async merge API can merge individual or stacked pull requests, add pull requests to a merge queue, or merge pull requests directly. It can optionally bypass rules when the caller has permission.
Sources: GitHub async merge API generally available - GitHub Changelog
How to use it
Submit a merge request with PUT, then poll with GET using the returned request ID to check its status. Because processing is asynchronous, automations do not have to wait for a complex merge to finish in one request.
GitHub recommends this API for programmatic pull request merges instead of the synchronous REST endpoint or GraphQL mutations. It is also the only merge API GitHub says supports stacked pull requests.
Sources: GitHub async merge API generally available - GitHub Changelog
AI assisted reporting, checked against the linked official sources. Source pages checked 2026-10-01. Editorial process and corrections.