feat(autofix): Trigger PR iteration runs and surface PR links in prompts#117216
Merged
Conversation
00707ec to
ccbb882
Compare
27bba00 to
1dfa019
Compare
1dfa019 to
46d270f
Compare
ccbb882 to
eed3d35
Compare
eed3d35 to
651fd65
Compare
651fd65 to
2f69801
Compare
2f69801 to
eed3d35
Compare
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit eed3d35. Configure here.
eed3d35 to
17c6766
Compare
Add the autofix-pr-iteration feature flag and wire the trigger path for the PR_ITERATION step. trigger_autofix_agent now persists the flag value in run metadata on creation, computes the iteration index (from the insert index on retry, otherwise the latest + 1), and includes it in the started webhook payload, prompt metadata, and trigger metric. build_step_prompt threads the run state into the prompt builders so pr_iteration_prompt can surface the open pull request links. Adds get_latest_iteration_index, get_iteration_for_insert_index, and recover_iteration_feedback helpers. Co-Authored-By: Claude Opus 4 <noreply@anthropic.com>
17c6766 to
3d52218
Compare
Replace the loose `Callable[..., str]` type on `StepConfig.prompt_fn` with a `PromptBuilder` Protocol that captures the exact keyword signature shared by all four step prompt builders. This lets mypy verify the STEP_CONFIGS registry and call site, and catches signature drift in any individual builder. No behavior change. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.

Add the autofix-pr-iteration feature flag and wire the trigger path for the
PR_ITERATION step. trigger_autofix_agent now persists the flag value in run
metadata on creation, computes the iteration index (from the insert index on
retry, otherwise the latest + 1), and includes it in the started webhook
payload, prompt metadata, and trigger metric. build_step_prompt threads the
run state into the prompt builders so pr_iteration_prompt can surface the open
pull request links. Adds get_latest_iteration_index, get_iteration_for_insert_index,
and recover_iteration_feedback helpers.
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.