Projects: expose repository list state to the import page - #13244
Draft
ericholscher wants to merge 1 commit into
Draft
Projects: expose repository list state to the import page#13244ericholscher wants to merge 1 commit into
ericholscher wants to merge 1 commit into
Conversation
Expose whether the user has a Git provider connected and any synced repositories in the import page context, so the dashboard can explain an empty repository list (provider not connected, or GitHub App with no repositories granted) instead of showing a search box with no results. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019yjYstmBb2HiscZUc5eKH4
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
2 participants
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.
The import page renders the same whether a user has repositories to pick from, connected an account that can never list repositories (Google or SSO only), or connected a Git provider whose sync found nothing — for example when our GitHub App isn't installed yet. The dashboard templates can't explain an empty repository list without knowing which of these states the user is in, so today the page fails silently and users stall at the exact step where we lose most of them.
This adds three context flags the theme's empty states branch on (companion PR in ext-theme). Things a reviewer may want to double-check: the "connected a Git provider" check derives the provider list from the OAuth service registry rather than hardcoding it, deliberately excluding identity-only providers like Google — this is stricter than the form prevalidation, which counts any social account; and repository visibility uses the same queryset as the repository list API, so the flag matches what the picker would actually show.
Generated by Claude Code