Dessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 17 days agoWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square20linkfedilinkarrow-up124arrow-down11
arrow-up123arrow-down1external-linkWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comDessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 17 days agomessage-square20linkfedilink
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up2arrow-down1·17 days agoYes, that’s what I said.
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up1·edit-217 days agoThen why mention setting up remotes? Why would multiple worktrees help if a worktree is not necessary for the functionality?
minus-squareatzanteol@sh.itjust.workslinkfedilinkEnglisharrow-up3arrow-down1·17 days agoThe question I was answering was about worktrees vs. multiple clones. With multiple clones you need to setup remotes to share branches between directories. With worktrees sharing a working copy you don’t.
Yes, that’s what I said.
Then why mention setting up remotes? Why would multiple worktrees help if a worktree is not necessary for the functionality?
The question I was answering was about worktrees vs. multiple clones. With multiple clones you need to setup remotes to share branches between directories. With worktrees sharing a working copy you don’t.