fix(ci): Add github_token to fix OIDC auth error in issue workflows#1011
fix(ci): Add github_token to fix OIDC auth error in issue workflows#1011
Conversation
When external users (without write access) create issues, the OIDC token exchange fails with "User does not have write access" error. Adding explicit github_token bypasses this authentication flow.
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
WalkthroughAdds Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes
Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (3)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
🔇 Additional comments (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying repomix with
|
| Latest commit: |
eb25412
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://cef53ef1.repomix.pages.dev |
| Branch Preview URL: | https://fix-claude-action-oidc-auth.repomix.pages.dev |
PR Review: fix(ci): Add github_token to fix OIDC auth error in issue workflowsSummaryThis PR fixes OIDC authentication failures for external users creating issues by explicitly passing ✅ StrengthsWorkflow Changes:
Documentation:
📋 ObservationsSchema File Addition (Auto-generated)The Note: This file is missing a trailing newline at the end (line 163), which differs from other schema files. This is a very minor issue and not blocking.
|
| Scenario | Risk | Mitigation |
|---|---|---|
| Token scope insufficient | Low | The workflow already has issues: write permission, which GITHUB_TOKEN respects |
| Breaking change for users | None | This is an internal workflow; no public API changes |
| Schema versioning issues | Low | Auto-generated schema matches existing patterns |
Verdict
LGTM ✅ - This is a straightforward fix for a real authentication problem. The change is minimal, well-documented, and follows established patterns.
🤖 Generated with Claude Code
When external users (without write access) create issues, the OIDC token exchange in
claude-code-actionfails with:This PR adds explicit
github_token: ${{ secrets.GITHUB_TOKEN }}to bypass the OIDC token exchange and use the workflow's built-in token instead.Affected workflows:
claude-issue-similar.ymlclaude-issue-triage.ymlNote: Comments will now be posted as
github-actions[bot]instead ofclaude[bot].Checklist
npm run test(N/A - workflow changes only)npm run lint(N/A - workflow changes only)