Dessalines@lemmy.ml to Programming@programming.dev · 2 months agoWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square22fedilinkarrow-up1120arrow-down11cross-posted to: programming@lemmy.ml
arrow-up1119arrow-down1external-linkWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comDessalines@lemmy.ml to Programming@programming.dev · 2 months agomessage-square22fedilinkcross-posted to: programming@lemmy.ml
minus-square6nk06@sh.itjust.workslinkfedilinkarrow-up3·2 months ago it seems very similar to just “git cloning” Worktrees take less space, and the fetch/pull only has to be done once. It’s a nice feature but restricted to workflows where you work on a lot of features at the same time.
Worktrees take less space, and the fetch/pull only has to be done once. It’s a nice feature but restricted to workflows where you work on a lot of features at the same time.