chore(ci): surface bun exit code with ::warning:: on failure - #42151
chore(ci): surface bun exit code with ::warning:: on failure#42151niStee wants to merge 1 commit into
Conversation
Wrap the bun script invocation so a non-zero exit code emits a ::warning:: annotation visible in the run log, making the failure mode (GraphQL error, token-scope error, unhandled exception) easier to diagnose without reading the full log. The exit code is still propagated (exit $exit_code), so the workflow step still fails — but now the failure reason is visible at a glance in the run summary.
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
Hey! Your PR title Please update it to start with one of:
Where See CONTRIBUTING.md for details. |
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
|
@anomalyco not sure what's still missing regarding your contributing guidelines. |
Summary
Wrap the
bun script/github/close-prs.tsinvocation in.github/workflows/close-prs.ymlso a non-zero exit code emits a::warning::annotation visible in the run log.Fixes #42157
Problem
When the close-prs bun script fails (GraphQL pagination error, token-scope error, unhandled exception), the workflow step fails silently — the error is buried in the full log with no visible annotation in the run summary. This makes diagnosing close-prs failures harder than necessary.
Fix
The exit code is still propagated (
exit $exit_code), so the workflow step still fails — but now the failure reason is visible at a glance in the run summary via the::warning::annotation.Verification
niStee/opencode(same workflow file, same failure mode observed in run Enhance custom commands #13)