You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: use check-success instead of status-success for GitHub Actions (#35188)
### Reason for this change
After removing the CodeBuild requirement from Mergify in #35174,
automatic PR merging stopped working. Mergify was looking for
status-success=validate-pr and status-success=build, but GitHub Actions
creates check runs, not statuses. CodeBuild used the GitHub Status API,
while GitHub Actions uses the GitHub Checks API.
### Description of changes
Changed all Mergify conditions from status-success=validate-pr and
status-success=build to check-success=validate-pr and
check-success=build to match what GitHub Actions actually creates.
The previous configuration worked because Mergify was only waiting for
the CodeBuild status (which was correctly configured), while the GitHub
Actions conditions were silently failing but not blocking merges.
### Describe any new or updated permissions being added
NA
### Description of how you validated changes
Analyzed GitHub API responses for recent PRs to confirm:
• CodeBuild creates statuses via GitHub Status API
• GitHub Actions creates check runs via GitHub Checks API
• Verified that approved PRs have successful validate-pr and build check
runs but no corresponding statuses
### Checklist
- [x] My code adheres to the [CONTRIBUTING
GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and
[DESIGN
GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)
----
*By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache-2.0 license*
0 commit comments