Skip to content

Commit f4eb49d

Browse files
Tr1Fecta-7claude
andcommitted
docs(user): explain projects with several repositories
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 3ca8e32 commit f4eb49d

1 file changed

Lines changed: 15 additions & 0 deletions

File tree

‎docs/user/source-control.md‎

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,21 @@ For a local Git repository without a remote, **Publish Repository** creates a ho
9999
adds it as `origin`, and pushes your commits. If there are no commits yet, it creates the remote;
100100
make your first commit before pushing.
101101

102+
## Projects with several repositories
103+
104+
To work across several repositories in one thread, add the folder that holds them as the project.
105+
T3 Code treats every folder directly inside it that is a Git repository as part of the project. If
106+
the folder contains one VS Code `.code-workspace` file, the repositories it lists count instead,
107+
named the way the file names them. Repositories outside the project folder are not included.
108+
109+
Each repository gets its own Git actions in the thread panel, and turn diffs and rewinds cover all
110+
of them. In the diff panel, **Uncommitted** and **Changes** show one repository at a time; pick it
111+
next to the scope. **New worktree** gives the thread its own copy of every repository on one branch,
112+
each starting from that repository's default branch. The project's other top-level files and
113+
folders are linked into that copy rather than duplicated, so edits to them change the originals.
114+
With a `.code-workspace` file, only the folders it lists are linked, along with top-level files and
115+
dot-folders.
116+
102117
## Create a pull request
103118

104119
Use a thread's Git actions to commit, push, and create a pull request. T3 Code can generate commit

0 commit comments

Comments
 (0)