gha: raise AI-assisted backport max-turns to 80#30320
Open
Conversation
Single-commit backports with one content conflict can use 25-35 turns once preflight friction is accounted for, leaving little headroom under the previous 40-turn cap. Multi-commit chains with empty/skipped cherry-picks routinely exceed it. 80 covers ~95% of cases that reach the AI fallback path. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
andrewhsu
requested review from
PrzemekZglinicki
and removed request for
a team
Contributor
There was a problem hiding this comment.
Pull request overview
Raises the Claude Code Action --max-turns limit for the AI-assisted backport fallback workflow to reduce failures caused by hitting the previous turn cap.
Changes:
- Increased
--max-turnsfrom 40 to 80 for the Claude-driven AI fallback in the backport workflow.
Contributor
Did you consider updating instructions so it doesn’t burn these turns? |
PrzemekZglinicki
approved these changes
Apr 28, 2026
Contributor
|
Sorry about that I was trying to figure out why the go linter failed and could not figure out how to fix it for that PR, just ended up closing that manually backported PR. |
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
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.
Run 25047762576 hit the 40-turn limit while backporting #30302 (1 commit, 43 LOC, single content conflict). Walking the turn log:
cd <dir> && git ...blocked,mkdiroutside the action's session dir blocked).git show/grep/sedof HEAD vs incoming).cherry-pick --continueand verification.git push --set-upstreamfrom the prompt never ran — the model's final tool batch overran turn 40.A second recent failure (25015920693, backport of #30169 — 19 commits) hit the same cap. That one needs more than 80 even after this bump; tracked separately as a skill optimization (skip empty cherry-picks without investigating parents).
Distribution of source PRs in the last 50 v26.1.x backports:
80 is enough for ~95% of cases that reach the AI fallback path. The flag only caps; it doesn't cost anything when unused.
Tracked under DEVPROD-4165.
Backports Required
UX Changes
Release Notes