anomalyco / anomalyco/opencode

[BUG]: close-prs workflow failures are silent in the run log — no ::warning:: annotation

Open
#42,157 1 comment 0 reactions 1 assignee View on GitHub

@nexxeln is already working on this.

Since Aug 12, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

When the close-prs workflow (.github/workflows/close-prs.yml) runs bun script/github/close-prs.ts and the 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 ::warning:: annotation in the run summary.

This makes diagnosing close-prs failures unnecessarily hard — the run shows "failed" but you have to download and read the full log to find the error.

Plugins

N/A

OpenCode version

N/A (this is a CI workflow issue, not a runtime bug)

Steps to reproduce

  1. Wait for the scheduled close-prs workflow to run (daily at 22:00 UTC)
  2. If script/github/close-prs.ts exits non-zero (e.g., GraphQL token-scope error, unhandled exception)
  3. The workflow step fails with no annotation in the run summary — only the raw exit code in the log

Screenshot and/or share link

N/A — this is a CI workflow observability issue, not a UI bug.

Operating System

GitHub Actions (ubuntu-latest)

Terminal

GitHub Actions runner

Proposed fix

Wrap the bun invocation so a non-zero exit code emits a ::warning:: annotation:

bun script/github/close-prs.ts "${args[@]}" || {
  exit_code=$?
  echo "::warning::close-prs.ts exited with code $exit_code — check logs for GraphQL/token-scope errors"
  exit $exit_code
}

The exit code is still propagated, so the workflow step still fails — but the failure reason is visible at a glance in the run summary.

PR: #42151

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.