Find the repository somebody points at - #8
Merged
Merged
Conversation
Choosing a project folder — one with a .git in it — answered "no repositories found in here". The chosen folder was only ever a place to look inside, and the .git that proves it is a repository is hidden, so the picker would not let it be chosen either: there was no way to say "this one". A chosen folder under git is now that project. A chosen folder with only a .claude still means look inside — that is ~/Projects with house instructions at the top, which once read as a single project and hid ninety — and becomes the project only when nothing turned up under it. The picker and Settings now say a repository itself is a valid answer.
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
1 participant
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.
Reported on Reddit after installing 0.3.4: a person gave Loadout their project directory — a checkout with a
.gitand an.opencodein it — and was told "No repositories found in here". They then tried to choose the.opencodeinside it, which is hidden and cannot be selected in the panel. There was no way to say "this folder is the project".The search treated a chosen folder as a place to look inside, never as an answer. That rule exists for a real shape:
~/Projectswith a.claudeof its own at the top read as one project and hid ninety.So the rule is now split by marker:
.gitis that project — what is nested in a checkout is its submodules and packages, not other projects;.claudestill means look inside, and is taken as the project only when nothing turned up under it.Nested behaviour, depth,
node_modules, and de-duplication are unchanged. The picker, Settings and the welcome sheet now say a repository itself is a valid answer, since nothing on screen did.Four tests cover it: pointing at a repository, pointing at one that contains submodules, house instructions losing to what is inside them, and an ordinary empty folder still finding nothing. Full suite: 303 passing.