Repository navigation
fix: correlate CI checks with the exact commit - #167
tridev-tej wants to merge 5 commits into
Conversation
GitHub reports STARTUP_FAILURE when a workflow can't start. It was missing from the completed-conclusion buckets, so the watcher raised KeyError, returned status=error and never reached the fixer. Map it to fail like the other terminal failures; the new test drives a startup failure through the watcher to the fixer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
|
|
Thanks for fixing #159. The exact-commit watcher now handles head movement, missing vs pending checks, commit statuses, re-runs and pagination without accepting results from an older commit. I pushed one small follow-up (55b43ce): Validated the merge with main:
This is ready to merge once the CLA is signed. |
Summary
The watcher stops because
gh pr checksrejectsheadSha. I switched it to commit-scoped GraphQL checks, preserved distinct check identities and followed fixer commits. Watcher payloads are validated before the fixer runs; ordinary failed/error envelopes returnerrorat that boundary.Validation
make checkBehavior Impact
Notes
No migration. Closes #159.