this post was submitted on 26 Jul 2024
32 points (100.0% liked)

Git

2899 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS
Ategon@programming.dev
canpolat@programming.dev
jnovinger@programming.dev
32
How I Use Git Worktrees - Alex Kladov (matklad.github.io)
submitted 4 months ago by mac@programming.dev to c/git@programming.dev
14 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] lobut@lemmy.ca 6 points 4 months ago* (last edited 3 months ago) (1 children)

I use worktrees and I wondered the same question, so far here's what I like:

git worktrees list can show all the worktrees, you have for this same repo (not crazy value, I know)

git fetch applies to all your worktrees

git stash / apply can work across worktrees, so I can stash in one and apply it to another

You're limited to a specific branch per worktree and many don't like that but I typically work from a detached HEAD anyways.

[–] nous@programming.dev 3 points 4 months ago

And cherry-pick commits done on different work trees without syncing them first. Or rebase or mergeworkk done on one work tree with others. Or check commit logs or diff them.