Skip to content

fix: use built-in GITHUB_TOKEN instead of requiring it as secret - #3

Merged
isuttell merged 1 commit into
mainfrom
fix/rename-github-token-secret
Dec 7, 2025
Merged

isuttell merged 1 commit into
mainfrom
fix/rename-github-token-secret

Conversation

@isuttell

@isuttell isuttell commented Dec 7, 2025

Copy link
Copy Markdown
Contributor

Summary

  • Remove github_token from workflow_call secrets (reserved name collision)
  • Use secrets.GITHUB_TOKEN directly in workflows (automatically available)
  • Update README and CLAUDE.md documentation

Changes

The github_token secret name collides with GitHub's reserved name in workflow_call. This fix removes the requirement for callers to pass it, and instead uses the automatically provided secrets.GITHUB_TOKEN directly.

Risk Assessment

LOW - Uses built-in GitHub functionality that's more reliable than manual secret passing.

🤖 Generated with Claude Code

The `github_token` secret name collides with GitHub's reserved name
in workflow_call. Instead of requiring callers to pass it, use the
automatically provided `secrets.GITHUB_TOKEN` directly.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@isuttell
isuttell merged commit 2386147 into main Dec 7, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant