[k11kirky]

Problem

When a GitHub connection attempt fails, the error is shown as a toast notification that disappears quickly, leaving users with no clear indication of what went wrong or how to recover. Error codes returned from GitHub's OAuth flow are not translated into human-readable messages, making it difficult for users to understand and resolve the issue.

Changes

• Adds an "error" state to useGithubUserConnect, replacing the previous behavior of silently resetting to "idle" and firing a toast on failure
• Exposes the error object and a reset function from useGithubUserConnect so callers can inspect and clear the error
• Introduces describeGithubConnectError, which maps known GitHub OAuth error codes (e.g. access_denied, invalid_state, installation_not_authorized) to plain-language messages
• Updates GitHubConnectionBanner to display the human-readable error message inline in the banner with a "Click to try again" prompt, resetting state on click
• Updates GitIntegrationStep (onboarding) to show the error message in red with "Try again" and "Dismiss" buttons instead of silently failing
• Passes structured { message, code } error objects through useGitHubIntegrationCallback instead of raw strings, enabling error-code-aware messaging across all connection surfaces

[k11kirky]

• feat(code): list all GitHub installations and allow adding another org #2001
• feat(code): detect stale GitHub integration and offer Reconnect #2000
• feat(code): add inline GitHub disconnect to onboarding step #1999
• feat(code): show persistent error state for GitHub connect failures #1998 👈 (View in Graphite)
• feat(code): show fast-path GitHub sign-in when current project has team install #1997
• feat(code): unify user-scoped GitHub connect into a shared hook #1996
• feat(code): cleaner GitHub integration onboarding step #1990
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
apps/code/src/renderer/features/inbox/components/list/GitHubConnectionBanner.tsx:44-45
**Redundant retry language in error label**

Most entries in `ERROR_MESSAGES` already end with "Please retry." or "Try again" phrasing. Appending `" Click to try again."` produces doubled retry prompts — e.g. `"GitHub returned an error during sign-in. Please retry. Click to try again."` — which reads awkwardly for the majority of error codes. Consider either stripping the retry CTA from the `ERROR_MESSAGES` strings or removing the suffix from the template literal.

_{Reviews (1): Last reviewed commit: "feat(code): show persistent error state ..." | Re-trigger Greptile}

[greptile-apps]

Redundant retry language in error label

Most entries in ERROR_MESSAGES already end with "Please retry." or "Try again" phrasing. Appending " Click to try again." produces doubled retry prompts — e.g. "GitHub returned an error during sign-in. Please retry. Click to try again." — which reads awkwardly for the majority of error codes. Consider either stripping the retry CTA from the ERROR_MESSAGES strings or removing the suffix from the template literal.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/inbox/components/list/GitHubConnectionBanner.tsx
Line: 44-45

Comment:
**Redundant retry language in error label**

Most entries in `ERROR_MESSAGES` already end with "Please retry." or "Try again" phrasing. Appending `" Click to try again."` produces doubled retry prompts — e.g. `"GitHub returned an error during sign-in. Please retry. Click to try again."` — which reads awkwardly for the majority of error codes. Consider either stripping the retry CTA from the `ERROR_MESSAGES` strings or removing the suffix from the template literal.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[k11kirky]

Merge activity

• May 4, 2:36 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 4, 2:57 PM UTC: Graphite rebased this pull request as part of a merge.
• May 4, 3:04 PM UTC: @k11kirky merged this pull request with Graphite.