fix: use GH_TOKEN for GitHub CLI in release-trigger workflow#8
Merged
jonasbokim merged 1 commit intomainfrom Mar 8, 2026
Merged
fix: use GH_TOKEN for GitHub CLI in release-trigger workflow#8jonasbokim merged 1 commit intomainfrom
jonasbokim merged 1 commit intomainfrom
Conversation
The gh CLI tool specifically requires GH_TOKEN environment variable, not GITHUB_TOKEN. Also changed from RELEASE_PAT to GITHUB_TOKEN to use the automatically provided token.
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
1 participant
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.
The gh CLI tool specifically requires GH_TOKEN environment variable, not GITHUB_TOKEN. Also changed from RELEASE_PAT to GITHUB_TOKEN to use the automatically provided token.
Description
Testing
uv run specify --helpuv sync && uv run pytestAI Disclosure