ci: allow maintainers to run the module scorecard on fork PRs via /scorecard - #1065
Open
bpmct wants to merge 3 commits into
Open
ci: allow maintainers to run the module scorecard on fork PRs via /scorecard#1065bpmct wants to merge 3 commits into
bpmct wants to merge 3 commits into
Conversation
bpmct
marked this pull request as ready for review
August 19, 2026 21:40
bpmct
changed the title
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
2 participants
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.
Fork PRs currently get no scorecard comment because they don't have access to secrets. This adds an
issue_commenttrigger: a maintainer comments/scorecardon a community PR to run the check on demand. Same-repo PRs keep the automaticpull_requestbehavior, unchanged.The first version of this used
pull_request_target, which zizmor rightly blocked. This approach avoids it:issue_commentruns in the base-repo context, the maintainer restriction (OWNER/MEMBER/COLLABORATOR) makes every fork-PR scoring an explicit human decision, and it doubles as cost control for the Anthropic API.Discussions are not affected. PR mode only reads them for the baseline, and the token only has
discussions: readanyway.To keep secrets safe, the scoring scripts always run from the base repo. PR content is fetched via
refs/pull/N/mergeand only pulled in underregistry/coder/modules/, read as plain text for the prompt, never executed.🤖 Generated with Coder Agents on behalf of @bpmct