Repository navigation
[autopilot] skills: stale gh token env vars in reproducing-ci-locally - #160
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a short note and checklist line: when a shell profile exports a stale GITHUB_TOKEN/GH_TOKEN, the CLI reports an invalid token even though a working stored login exists; unset the variables for the command (env -u) rather than re-authenticating, including when reading CI status to confirm a run. Motivated by a recurring pattern of environment-variable credentials silently overriding a good login during CI confirmation. Same shape as the existing VIRTUAL_ENV guidance in that skill. No registration changes (existing skill).