Skip to content

feat(autofix): Stop PR iteration from an @sentry comment - #122477

Draft
alexsohn1126 wants to merge 5 commits into
alexsohn/cw-1709-allow-iteration-pause-and-resumefrom
alexsohn/cw-1709-stop-pr-iteration-from-comment
Draft

feat(autofix): Stop PR iteration from an @sentry comment#122477
alexsohn1126 wants to merge 5 commits into
alexsohn/cw-1709-allow-iteration-pause-and-resumefrom
alexsohn/cw-1709-stop-pr-iteration-from-comment

Conversation

@alexsohn1126

Copy link
Copy Markdown
Member

Adds an @sentry stop iterating command on top-level pull request comments. It calls the existing pause_pr_iteration, which had no production caller until now.

Two words, not one: @sentry stop putting long comments in the diff is real feedback and still iterates.

The command runs the same gates as an iteration — feature flag, GitHub provider, repo write access. It acknowledges with a 👍 and a comment, and reports a failure with a 😕 when the run has no SeerRun row to mark.

Stacked on #122086.

CW-1709

@linear-code

linear-code Bot commented Aug 24, 2026

Copy link
Copy Markdown

CW-1709

@github-actions github-actions Bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Aug 24, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

Add an `@sentry stop iterating` command on top-level pull request comments.
The command calls the existing `pause_pr_iteration`, which was previously
unreachable from production code.

The two-word phrase avoids a collision with real feedback such as
`@sentry stop putting long comments in the diff`, which still iterates.

The command runs the same gates as an iteration: the feature flag, the
GitHub provider check, and repo write access. It acknowledges with a 👍
and a comment, and reports a failure with a 😕 when the run has no
SeerRun row to mark.
@alexsohn1126
alexsohn1126 force-pushed the alexsohn/cw-1709-stop-pr-iteration-from-comment branch from 2606843 to 918e502 Compare August 24, 2026 16:25
@alexsohn1126 alexsohn1126 removed the Scope: Frontend Automatically applied to PRs that change frontend components label Aug 24, 2026
… alexsohn/cw-1709-stop-pr-iteration-from-comment
… alexsohn/cw-1709-stop-pr-iteration-from-comment
Cut the stop confirmation to one sentence. Split the footer onto two
lines and drop the review caveat.

Also assert the iterate task's unauthorized metric name, which nothing
covered.
A blank line closes the markdown block, so the second line rendered
outside the sub tag. Wrap each line in its own tag.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant