Dessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 1 month agoWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square20fedilinkarrow-up125cross-posted to: git@programming.devprogramming@programming.dev
arrow-up125external-linkWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comDessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 1 month agomessage-square20fedilinkcross-posted to: git@programming.devprogramming@programming.dev
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up1·edit-21 month 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-up3·1 month 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.
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.