git-worktree

问题 I like to keep on repository checked out in several worktrees with git worktree to easily work on different branches simultaneously. Yet VS code does not seem to recognize git as scm when it is in a git worktree folder. I couldn't find anything in the docs about this or an extension. Are there any ideas on how I could get VS code to support git features in an external worktree? 回答1: I didn't think this would matter, but it turns out... I'm on Windows and run my git command line in Windows

问题 When I do git worktree list , it display follows. /path/to/workspace c943d35 [master] /path/to/workspace ef4df56 (detached HEAD) It is my working directory (not worktree directory). I do not know how it happened, and how to clean it. I've try git worktree prune , but it does not change anything. Any help will be appreciated. Many thanks. 回答1: git worktree -- details mentions: Each linked working tree has a private sub-directory in the repository’s $GIT_DIR/worktrees directory. Check the

问题 When I do git worktree list , it display follows. /path/to/workspace c943d35 [master] /path/to/workspace ef4df56 (detached HEAD) It is my working directory (not worktree directory). I do not know how it happened, and how to clean it. I've try git worktree prune , but it does not change anything. Any help will be appreciated. Many thanks. 回答1: git worktree -- details mentions: Each linked working tree has a private sub-directory in the repository’s $GIT_DIR/worktrees directory. Check the

问题 I'm using Git Extensions for my projects. I really like it. There is an issue that keeps bugging me and I'm pretty sure there is a trick in Git Extensions for it. Here is the scenario: From master branch, I created 3 branches A , B and C . Started working in branch A , did some changes Switched to branch B , I still see changes made in A as they are not committed I don't want to commit changes in A because I'm not done yet and I don't want this commit to appear in commit history I don't want

来源： https://stackoverflow.com/questions/64457757/how-to-create-a-git-repo-without-a-working-directory

来源： https://stackoverflow.com/questions/54582558/git-pull-merge-changes-is-worktrees

问题 For use with worktrees, I'm trying to make a bare clone but where remote branches are mapped to remote tracking branches. I'm trying to set up a generic worktree workflow. My repo is really really big, so cloning it is expensive. And even using hard links, as repos get gc ed, they tend to diverge over time and use up extra space, and a fetch in one repo is does not help another, so working in worktrees seems the obvious thing to do. (You'll have to trust me on this.) Worktrees require a 'main

问题 For use with worktrees, I'm trying to make a bare clone but where remote branches are mapped to remote tracking branches. I'm trying to set up a generic worktree workflow. My repo is really really big, so cloning it is expensive. And even using hard links, as repos get gc ed, they tend to diverge over time and use up extra space, and a fetch in one repo is does not help another, so working in worktrees seems the obvious thing to do. (You'll have to trust me on this.) Worktrees require a 'main

问题 Just when I thought Git couldn't get any more complicated, I just discovered git worktree. Either this is a synonym for subtree or feature I never knew about. Is worktree the same as subtree or are they different. If they are different, how are they different and what problem does worktree solve? 回答1: These are very different. To understand them properly, let's define work-tree (or "work tree" or "working tree" or pretty much any variant of these spellings), with respect to the index and to

问题 I'd like to use local file exclusion on a worktree. I tried adding the file name to .git/worktrees/$worktreename/info/exclude but it doesn't take. The analogous file .git/info/exclude works, but applies to all worktrees, not just the main one. 回答1: but it doesn't take From this thread, it should, but if you are working with Visual Studio, it does not. Make sure to try with the latest 2.16.x version of Git to see if the issue persists. Note that I do not see an info/exclude in .git/worktrees