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
{{ message }}
Repository navigation
Check-in runner GITHUB_TOKEN is invalid and blocks the CI probe #145
The GITHUB_TOKEN on the check-in runner is invalid, so the CI probe returns HTTP 401 and no workflow state reaches the archive.
Target:scripts/tools/daily-checkin-data.mjs (GITHUB_TOKEN in the routine runner environment)
Verify with:gh auth status reports a valid token, then node scripts/tools/daily-checkin-data.mjs archives ci.workflows states
Estimated to change 1 file.
The daily-checkin routine opened this issue automatically on its 2026-09-05T21:40:00.000Z run. It is not Harlan's own report. Close it to reject the proposal, and the reason you give stops it being offered again.
Summary: Reproduced live in the prepared worktree: the runner environment exports an expired fine-grained PAT (github_pat_, 94 chars) as GITHUB_TOKEN, and the gh CLI prefers that env var over the valid keyring login, so every gh call in the ci probe
Next action: Implement the fallback in scripts/tools/daily-checkin-data.mjs: on gh auth failure under the inherited GITHUB_TOKEN, validate with gh auth status and strip the rejected env var from the child-process env (run() at line 36) so gh uses the ke
Activity
harlan-github-agent commentedon Sep 6, 2026
🤖 ISSUE TRIAGE
fix: resolve issue #145
harlan-zw commentedon Sep 7, 2026
Fixed by #133 (merged 2026-09-07): gh falls back to its keyring login when the runner token is rejected.