Clearer mergability information for Pull Requests
The area above the merge button now contains more information, making it easier to see if your proposed changes are ready to go or need more work. Each month, 119,000…
The area above the merge button now contains more information, making it easier to see if your proposed changes are ready to go or need more work.
Each month, 119,000 repositories on GitHub use automated status checks (via the GitHub Statuses API) and it’s important that this information is presented in a way that you can easily understand. When you’re ready to merge a pull request, you should be able to see that it is ready. If a check isn’t passing, you should be able to see why.
Here’s a refresher on how to merge a pull request.
Written by
Related posts
An update on GitHub availability
Here’s what we’ve done—and what we’re still doing—to improve our availability and reliability.
GitHub Copilot is moving to usage-based billing
Starting June 1, your Copilot usage will consume GitHub AI Credits.
Changes to GitHub Copilot Individual plans
We’re making these changes to ensure a reliable and predictable experience for existing customers.