Skip to content

fix(inbox): Show retry CTA when Seer produces no code changes - #122464

Draft
roggenkemper wants to merge 4 commits into
masterfrom
roggenkemper/iswf-3280-retry-cta
Draft

fix(inbox): Show retry CTA when Seer produces no code changes#122464
roggenkemper wants to merge 4 commits into
masterfrom
roggenkemper/iswf-3280-retry-cta

Conversation

@roggenkemper

@roggenkemper roggenkemper commented Aug 24, 2026

Copy link
Copy Markdown
Member

When Seer completes the code changes step without producing a diff, the inbox preview still showed a "Create PR" CTA — there is nothing to open a PR from.

The action row now checks the completed code changes section for patches and, when there are none, renders "Add context & retry" instead. Clicking it opens the reset prompt the proposal section already renders inline (next to "No code changes were proposed."), so the retry happens in the preview rather than navigating to the Seer drawer.

To share that state, IssuePreview hoists the code changes retry context above both the action row and the Seer content; the proposal section still owns it when rendered without that provider. The patch lookup both call sites need is now getCodeChangePatches in useExplorerAutofix.

Fixes ISWF-3280

The next-step helper returns `create_pr` as soon as the code changes step
completes, even when the run produced no diff, so the inbox preview showed
"Create PR" for a run with nothing to open a PR from. Check the completed
section for patches and fall back to "Add context & retry", matching the
autofix panel on issue detail.
@linear-code

linear-code Bot commented Aug 24, 2026

Copy link
Copy Markdown

ISWF-3280

@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Aug 24, 2026
Hoist the code changes retry state into IssuePreview so the action row's
"Add context & retry" CTA opens the reset prompt the proposal section already
renders, rather than navigating to the Seer drawer to reach it. The proposal
section keeps owning that state when rendered without the enclosing provider.

Extract the shared patch lookup as getCodeChangePatches so the action row and
the proposal section can't drift.
Carry a one-time drawer action from the empty-code-changes CTA so the Seer context form is ready immediately.

Refs ISWF-3280
@github-actions

Copy link
Copy Markdown
Contributor

Story previews

Preview the stories changed in this PR on the Vercel deployment:

Preview deployment: https://sentry-jle0ahoze.sentry.dev

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

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant