Nudge users to enable the PR comment when github-token is missing - #163
Merged
Conversation
The default after upgrading to v0.1.0 (version bumped, but github-token + pull-requests: write not added) was a silent job-summary-only experience. Now, when a review link is produced on a pull_request but no github-token is set, emit a ::notice:: telling the user how to get it as a PR comment. Fires only with a review link + PR context, so no-changes runs and non-PR events stay quiet; fork PRs (read-only token present) keep the existing 403-fallback path. Co-Authored-By: Claude Opus 4.8 <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
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.
P0 launch-hardening (#1). After upgrading to v0.1.0 by bumping only the version (not adding
github-token+permissions: pull-requests: write), the freebreaking/changelogaction posted the review link to the job summary only, silently — the default for every upgrader, landing on the low-traffic surface the whole encrypted-review effort was meant to escape.Now, when a review link is produced on a pull request but no
github-tokenis set, the action emits a::notice::explaining how to get the review as a PR comment (with a docs link). It fires only when there's a review link + PR context, so no-changes runs and non-PR events stay quiet, and fork PRs (which have a read-only token present) keep the existing 403-fallback notice.🤖 Generated with Claude Code