Skip to content

Fix Claude OAuth token env for Actions#434

Merged
justin808 merged 1 commit into
masterfrom
jg-codex/claude-oauth-env-fallback
Jul 5, 2026
Merged

Fix Claude OAuth token env for Actions#434
justin808 merged 1 commit into
masterfrom
jg-codex/claude-oauth-env-fallback

Conversation

@justin808

Copy link
Copy Markdown
Member

Summary

  • pass CLAUDE_CODE_OAUTH_TOKEN through the Claude action step env as well as the existing with: input
  • keep OAuth token wiring consistent for Claude review and @claude workflows

Why

anthropics/claude-code-action@v1 can resolve the OAuth input empty in this runner path unless the token is also available in the inherited step env. This matches the Hichee fix proven by shakacode/hichee#9633.

Verification

  • workflow-only YAML patch generated from the org Claude integration audit

@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@justin808, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f18df10e-4afd-493c-b075-085667b7b9dc

📥 Commits

Reviewing files that changed from the base of the PR and between 6bd0566 and 75d3587.

📒 Files selected for processing (1)
  • .github/workflows/claude-code-review.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jg-codex/claude-oauth-env-fallback

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@justin808 justin808 merged commit e1aee79 into master Jul 5, 2026
2 of 3 checks passed
@justin808 justin808 deleted the jg-codex/claude-oauth-env-fallback branch July 5, 2026 06:08
@greptile-apps

greptile-apps Bot commented Jul 5, 2026

Copy link
Copy Markdown

Greptile Summary

This PR updates the Claude review workflow token wiring. The main changes are:

  • Adds CLAUDE_CODE_OAUTH_TOKEN to the Claude action step environment.
  • Keeps the existing claude_code_oauth_token action input.
  • Limits the new environment variable to the Claude action step.

Confidence Score: 5/5

This looks safe to merge.

  • No blocking issues found in the changed workflow.
  • The new token value is scoped to the Claude action step.
  • The same token was already passed to the action through its input.

Important Files Changed

Filename Overview
.github/workflows/claude-code-review.yml Adds step-scoped Claude OAuth token environment wiring while preserving the existing action input.

Reviews (1): Last reviewed commit: "Fix Claude OAuth token env for Actions: ..." | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant