projects: explain the empty repository list on the add project page - #770
Draft
ericholscher wants to merge 1 commit into
Draft
projects: explain the empty repository list on the add project page#770ericholscher wants to merge 1 commit into
ericholscher wants to merge 1 commit into
Conversation
Show connect, install, and sync guidance inline when the repository list is empty on page load, instead of only behind the post-search Repair popup. Cover the GitHub App in the organization approval guidance, prompt for installation when the App has no repositories yet, and add an Add project button to the dashboard empty state. 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.
A user who lands on the add project page with an empty repository list currently gets a search box that can never return results, and the guidance that would fix their situation (install the GitHub App, refresh the sync, request organization approval) is hidden behind the "Repair" popup that only appears after a failed search. Users who signed up with Google alone get the same dead end with no hint that they need to connect a Git provider at all.
This shows the right guidance inline on first load, branching on context from readthedocs/readthedocs.org#13244: no Git provider connected → connect prompt; connected but nothing synced → the repair guidance, with the GitHub App item distinguishing "never installed" from "installed but restricted". The organization-approval item previously rendered only for the legacy OAuth provider — explicitly not for the GitHub App, whose users are the ones that hit pending-approval installs — so it now covers both. The repair items move to a shared partial so the inline state and the Repair modal stay in sync. The dashboard's empty state also gains an Add project button; it previously only linked the tutorial.
Merge order is safe in both directions: the new states key on explicit
== Falsecomparisons, so until the application PR deploys, undefined context falls through to the current placeholder rather than showing the connect prompt to everyone. Worth double-checking that reasoning in review, since it's load-bearing.Generated by Claude Code