Skip to content

Increase max turns from 10 to 30 in workflow#1260

Merged
sbryngelson merged 1 commit intomasterfrom
claude-turns
Feb 24, 2026
Merged

Increase max turns from 10 to 30 in workflow#1260
sbryngelson merged 1 commit intomasterfrom
claude-turns

Conversation

@sbryngelson
Copy link
Copy Markdown
Member

@sbryngelson sbryngelson commented Feb 24, 2026

CodeAnt-AI Description

Increase Claude code review conversation limit from 10 to 30

What Changed

  • The GitHub Actions workflow for automated Claude code review now allows up to 30 conversational turns instead of 10
  • Longer multi-turn reviews can continue without being cut off, enabling more follow-up clarifications and iterative comments
  • No other workflow inputs or allowed tools were modified

Impact

✅ Longer automated code review conversations
✅ Fewer truncated review sessions
✅ More complete multi-step feedback in CI

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Copilot AI review requested due to automatic review settings February 24, 2026 16:48
@codeant-ai
Copy link
Copy Markdown
Contributor

codeant-ai bot commented Feb 24, 2026

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Feb 24, 2026

Warning

Rate limit exceeded

@sbryngelson has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 14 minutes and 43 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 34c13b7 and aba4762.

📒 Files selected for processing (1)
  • .github/workflows/claude-code-review.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch claude-turns

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 and usage tips.

@sbryngelson sbryngelson merged commit b08eac0 into master Feb 24, 2026
14 checks passed
@sbryngelson sbryngelson deleted the claude-turns branch February 24, 2026 16:48
@codeant-ai codeant-ai bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Feb 24, 2026
@codeant-ai
Copy link
Copy Markdown
Contributor

codeant-ai bot commented Feb 24, 2026

CodeAnt AI finished reviewing your PR.

@github-actions
Copy link
Copy Markdown

Claude Code Review

Files changed: 1

  • .github/workflows/claude-code-review.yml

Summary

  • Increases the --max-turns limit for the Claude Code Review workflow from 10 to 30.
  • This is a single-line change with no effect on logic, security posture, or allowed tools.
  • The motivation is to allow longer multi-step reviews to complete without truncation on complex/large PRs.
  • The workflow already correctly uses pull_request_target with base-repo-only checkout, so the security model is unchanged.
  • The allowedTools allowlist remains the same — no new tool access is granted.

Findings

No correctness or security issues found. The change is safe, but the following improvement opportunities are worth considering:

1. Cost / runaway-turn risk (, line 32–35)

There is no timeout-minutes: on the job, and --max-turns 30 on a large PR could consume substantially more API credits than the current limit of 10. Consider adding a job-level timeout (e.g., timeout-minutes: 10) to bound wall-clock cost and prevent runaway runs on unusual inputs:

jobs:
  claude-review:
    runs-on: ubuntu-latest
    timeout-minutes: 10   # <-- add this

2. No early-exit guard (, prompt block)

The prompt instructs Claude to post exactly one top-level comment, but with 30 turns there is more opportunity for the model to post multiple partial comments before finishing. The prompt could be strengthened by explicitly prohibiting intermediate comments (e.g., "Do not post any comment until your review is complete and you are ready to post the final result").

3. Consider parameterising the turn limit ()

Hard-coding --max-turns 30 means future adjustments require another PR. A repository variable (e.g., vars.CLAUDE_MAX_TURNS) with a fallback default would make this easier to tune without touching workflow code:

--max-turns ${{ vars.CLAUDE_MAX_TURNS || '30' }}

Overall: safe to merge — the change is low-risk and addresses a real limitation (10 turns is tight for large diffs). The suggestions above are enhancements, not blockers.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR increases the maximum number of turns allowed in the Claude code review workflow from 10 to 30, enabling longer conversational interactions during automated code reviews.

Changes:

  • Updated the --max-turns parameter from 10 to 30 in the Claude arguments

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

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Development

Successfully merging this pull request may close these issues.

2 participants