Repository navigation
Conversation
- Add github_token explicitly to bypass OIDC requirement for fork PRs - Change pull-requests permission to write so action can post comments Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Collaborator
|
Why is this closed @EdiWeeks? |
Contributor
Author
|
The fix was applied to #90 and #91 PRs, so workflows are fixed. @BenGWeeks |
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.
Summary
github_tokenexplicitly to bypass OIDC requirement for fork PRspull-requestspermission fromreadtowriteso the action can post review commentsThis fixes the CI/CD failure on PR #91 and other PRs from forks, where OIDC token authentication fails because GitHub restricts OIDC tokens for fork PRs for security reasons.
Test plan
🤖 Generated with Claude Code