File tree Expand file tree Collapse file tree 1 file changed +4
-3
lines changed Expand file tree Collapse file tree 1 file changed +4
-3
lines changed Original file line number Diff line number Diff line change @@ -286,7 +286,8 @@ rules and how to access refs of one worktree from another.
286
286
In general, all pseudo refs are per-worktree and all refs starting with
287
287
`refs/` are shared. Pseudo refs are ones like `HEAD` which are directly
288
288
under `$GIT_DIR` instead of inside `$GIT_DIR/refs`. There are exceptions,
289
- however: refs inside `refs/bisect` and `refs/worktree` are not shared.
289
+ however: refs inside `refs/bisect`, `refs/worktree` and `refs/rewritten` are
290
+ not shared.
290
291
291
292
Refs that are per-worktree can still be accessed from another worktree via
292
293
two special paths, `main-worktree` and `worktrees`. The former gives
@@ -363,8 +364,8 @@ linked worktree `git rev-parse --git-path HEAD` returns
363
364
`/path/other/test-next/.git/HEAD` or `/path/main/.git/HEAD`) while `git
364
365
rev-parse --git-path refs/heads/master` uses
365
366
`$GIT_COMMON_DIR` and returns `/path/main/.git/refs/heads/master`,
366
- since refs are shared across all worktrees, except `refs/bisect` and
367
- `refs/worktree`.
367
+ since refs are shared across all worktrees, except `refs/bisect`,
368
+ `refs/worktree` and `refs/rewritten` .
368
369
369
370
See linkgit:gitrepository-layout[5] for more information. The rule of
370
371
thumb is do not make any assumption about whether a path belongs to
You can’t perform that action at this time.
0 commit comments