You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Pick the repository for Git actions when the project root is not a repo
#37775
Layout: a non-Git project folder with about 15 sibling repos plus shared agent context (.claude/). Threads edit several repos at once, mostly in the source checkouts, not in worktrees.
Why it matters: in a multi-repo workspace every repo has its own state: its own branch, its own uncommitted changes, its own commits, and its own PR against its own base branch. One feature usually touches several of them (an API change plus the frontend that uses it), and each part is reviewed, committed and merged separately. So the person needs to see each repo's changes on their own and act on that repo alone: create its branch, commit its files, push it, open its PR. A view of the workspace as one folder cannot do that, and that is the gap below.
Problem: the Git panel's cwd is thread.worktreePath ?? project.workspaceRoot. With a non-Git root it only offers "Initialize Git". Running git init in the parent does not help: the panel then shows the empty parent repo and lists the inner repos as untracked folders. So none of the branch, changes, commit, push or PR actions are usable for these threads.
#35476 adds a repository picker for Git actions, but only for repository worktrees attached to a thread. In that PR @CreepyGnome confirmed that choosing between source checkouts is a separate feature, so this is that feature on its own.
Proposal:
When the project root is not a Git repo, list the Git repos one or two levels below it (two levels also catches grouped worktree folders).
A repo picker in the Version Control section, stored per thread, defaulting to the repo the agent last touched.
Branch, changes, commit, push and PR actions run against the picked checkout.
Related: #7041 (multi-repo projects in general), #35476 (repository worktrees).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Layout: a non-Git project folder with about 15 sibling repos plus shared agent context (
.claude/). Threads edit several repos at once, mostly in the source checkouts, not in worktrees.Why it matters: in a multi-repo workspace every repo has its own state: its own branch, its own uncommitted changes, its own commits, and its own PR against its own base branch. One feature usually touches several of them (an API change plus the frontend that uses it), and each part is reviewed, committed and merged separately. So the person needs to see each repo's changes on their own and act on that repo alone: create its branch, commit its files, push it, open its PR. A view of the workspace as one folder cannot do that, and that is the gap below.
Problem: the Git panel's cwd is
thread.worktreePath ?? project.workspaceRoot. With a non-Git root it only offers "Initialize Git". Runninggit initin the parent does not help: the panel then shows the empty parent repo and lists the inner repos as untracked folders. So none of the branch, changes, commit, push or PR actions are usable for these threads.#35476 adds a repository picker for Git actions, but only for repository worktrees attached to a thread. In that PR @CreepyGnome confirmed that choosing between source checkouts is a separate feature, so this is that feature on its own.
Proposal:
Related: #7041 (multi-repo projects in general), #35476 (repository worktrees).
All reactions