Skip to content

[autopilot] skills: stale gh token env vars in reproducing-ci-locally #160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wdm0006 merged 1 commit into from
Oct 25, 2026
Merged

[autopilot] skills: stale gh token env vars in reproducing-ci-locally #160

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions skills/common/reproducing-ci-locally/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,13 @@ If you prefer `uv run`, pass `--no-sync`. And prefix with `env -u VIRTUAL_ENV`
when a shell profile exports one — otherwise the run is silently redirected into
an unrelated environment and its results mean nothing.

The same shape applies to credentials: a stale `GITHUB_TOKEN`/`GH_TOKEN` exported
by the shell profile takes precedence over a working stored login, so `gh` reports
"invalid token" even though `gh auth status` also lists a good keyring account.
Run the command with the variables unset instead of re-authenticating or editing
credentials: `env -u GITHUB_TOKEN -u GH_TOKEN gh pr checks`. Do this when you are
reading CI status to confirm a run, not only when pushing.

## Fix divergence in shared config, not in the workflow

When you find a difference, ask where the fix belongs. A flag added to the
Expand Down Expand Up @@ -264,6 +271,7 @@ Environment:
- [ ] venv created explicitly at CI's runtime version, with CI's extras
- [ ] Tools driven from that venv (`.venv/bin/python -m …` or `--no-sync`)
- [ ] `env -u VIRTUAL_ENV` when a shell profile exports one
- [ ] `env -u GITHUB_TOKEN -u GH_TOKEN gh …` when `gh` rejects a token but a stored login works
- [ ] Gating linter/formatter/toolchain pinned; local run uses the pinned version

Running:
Expand Down
Loading