Improve gh-pr-checks polling logs and case handling #44
+39
−34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
gh pr checkspolling more robust against transient/variant CLI output and API glitches by avoiding exact-case matching of the temporary "no checks reported" message and by avoiding false positives whenghreturns errors or empty output.Description
.github/actions/gh-pr-checks/action.ymlto readchecks_outputwithchecks_output="$(gh pr checks "$PR" 2>&1 || true)"and use case-insensitive matching viagrep -qi "no checks reported"before deciding to wait.[INFO] No checks yet (elapsed=${elapsed}s), waiting...logs,[INFO] Checks detected for PR #$PRon detection, asleep 4between polls, and honor the existingMAX_WAIT_SECONDSinput to time out.Testing
Codex Task