GitHub Async Merge API Now Generally Available
GitHub's async merge API is now out of beta and recommended for programmatically merging pull requests, supporting stacked and queued merges for improved automation.
What changed?
GitHub's async merge API is now generally available (GA). This new API lets developers merge individual or stacked pull requests, add them to a merge queue, or merge them directly. It processes merges asynchronously, making it better suited for automation in busy repositories. The async merge API replaces the previous synchronous REST endpoint and GraphQL mutation approaches and is currently the only API that supports merging stacked pull requests.
Why does it matter to an everyday developer?
This API significantly improves the automation landscape for repositories with high activity or complex merge scenarios. By submitting merge jobs asynchronously, developers no longer have to wait for potentially long-running merges to complete in a single request. The new capabilities—queuing merge requests, merging stacks, and (with permissions) bypassing rules—create smoother workflows for teams managing multiple related PRs. Developers relying on automation or tools that merge PRs programmatically should update their integration, as the async API is now the recommended and most capable method.
What can the developer do now?
Developers can migrate their existing merge automation to use the async merge API. This involves submitting a merge request using a PUT call, then polling the operation status with a GET request using the provided request ID. Teams working with stacked PRs or requiring advanced merge queues can now build more reliable workflows directly via GitHub APIs. The previous synchronous REST and GraphQL merge methods are no longer recommended, so developers integrating with GitHub's merge automation should prioritize adopting the new async approach.