Update the glimpse workflow to the current template - #44
Merged
Conversation
The template changed upstream in glimpse-cli: since v1.3.0 the CLI falls back to a built-in public token when GLIMPSE_TOKEN is not available, so the check runs on fork pull requests too instead of being skipped. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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 workflow that
glimpse initscaffolds changed upstream in glimpse-cli. This updates.github/workflows/glimpse.ymlto the current template.What changed:
GLIMPSE_TOKENis missing. Since glimpse-cli v1.3.0, the CLI falls back to a built-in public token that can run check and analyze. So fork pull requests and repos without the secret are gated too.GLIMPSE_TOKENsecret is still optional. Setting it gives higher rate limits and usage attribution.🤖 Generated with Claude Code