ref(autofix): Gate manual PR iteration UI behind its own feature flag - #121189
Merged
Conversation
alexsohn1126
changed the base branch from
master
to
alexsohn/cw-1778/disable-manual-pr-iteration-by-another-feature-flag-backend
August 4, 2026 17:23
Contributor
Story previewsPreview the stories changed in this PR on the Vercel deployment: Preview deployment: https://sentry-7zq175wys.sentry.dev |
alexsohn1126
force-pushed
the
alexsohn/cw-1778/disable-manual-pr-iteration-by-another-feature-flag-frontend
branch
from
August 4, 2026 17:24
1653977 to
d1c5d99
Compare
Contributor
Sentry Snapshot Testing
|
Frontend half of CW-1778, following the backend split. Only the affordances a user drives move to `autofix-pr-iteration-manual`: - `isRunValidForPrIteration`, which gates the feedback form in the pull-request next step - the feedback form and its reset behavior in the code changes card Iteration *reporting* is shared with automated CI iteration and accepts either flag: the "Iterating on PR…" progress copy, the feedback history, the version tag, and PR polling in the drawer (automated CI iteration pushes commits with no user action, so the drawer must still poll). `isResetEligible` is a behavior change, not just visibility: reset stays available once a PR exists only where reset opens the manual form, so automated-CI-only orgs keep the pre-iteration behavior. Both directions are now covered, verified by mutation.
alexsohn1126
force-pushed
the
alexsohn/cw-1778/disable-manual-pr-iteration-by-another-feature-flag-frontend
branch
from
August 4, 2026 17:47
d1c5d99 to
45e1c32
Compare
alexsohn1126
marked this pull request as ready for review
August 4, 2026 18:19
joseph-sentry
approved these changes
Aug 4, 2026
joseph-sentry
left a comment
Contributor
There was a problem hiding this comment.
i could see a way where we land the frontend change first since if we roll out the BE first we show the form in the FE still until we roll out the FE change and the form fails because the BE rejects that request bc the flag is not enabled
it's fine here bc this feature is still internal and not used heavily
alexsohn1126
deleted the
alexsohn/cw-1778/disable-manual-pr-iteration-by-another-feature-flag-frontend
branch
August 4, 2026 20:22
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.
Frontend half of CW-1778. Depends on #121180 (backend) for the new flag registration — land that first.
autofix-pr-iterationgates both manual and automated CI PR iteration, so automated CI iteration can't ship without also exposing the manual UI. The backend PR addedorganizations:autofix-pr-iteration-manual; this moves the user-driven affordances onto it.current ui when manual feature flag is of -- you can still see the automatic iterations in the form of feedback, but we removed the form to trigger the iteration with a manual feedback.
with the manual flag -- show manual feedback form again:
Fixes CW-1778