GitHub async merge API generally available
The GitHub async merge API is now generally available, allowing users to merge individual or stacked pull requests, add pull requests to merge queues, or merge pull requests directly.
You can now use the generally available GitHub async merge API to merge individual or stacked pull requests, add pull requests to a merge queue, or merge pull requests directly. This includes optionally bypassing rules if you have permission.
The API processes merges asynchronously, helping your automations handle busy repositories without waiting for complex merges to finish in a single request. Submit a merge request with PUT, then poll with GET using the returned request ID to check its status.
The async merge API is now the recommended path for programmatically merging pull requests instead of the synchronous REST endpoint or GraphQL mutations. It’s also the only merge API that supports stacked pull requests. Check out the async merge API documentation for request parameters and examples.
The post GitHub async merge API generally available appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
Improved detection for withdrawn Dependabot alerts
Dependabot now provides improved detection for withdrawn alerts that are no longer valid due to advisory or vulnerability changes. This makes it easier to identify and manage alerts that have been removed.
Search and filter for budgets now available
The Budgets and alerts page in GitHub billing settings now displays all budgets in a single searchable and filterable list, making it easier to manage multiple budgets.
Code scanning AI Scan metrics in security overview
Organization and enterprise administrators can now view metrics showing AI Scan findings generated and resolved in the security overview dashboard, providing visibility into the impact of AI-powered code scanning on pull requests.