6 ms·

git worktree. Godsend if you regularly need to work on multiple branches simultaneously.

• jayd16 6y ago
  What does worktree provide that a fresh local clone doesn't?
  • fiddlerwoaroof 6y ago
    Reduced disk space usage for large repositories. And a convenient way to manage all your clones
    • jayd16 6y ago
      I guess it reduces duplicating the history? Large files are by far the bulk of what I personally deal with so it don't think there's a real difference for me but I could see it helping.
      • fiddlerwoaroof 6y ago
        Yeah, it only stores the objects in the .git directory once.
  • MarkSweep 6y ago
    If it's a multi-gigabyte repo that you are cloning over a slow VPN, it speeds things up quite a bit.
    • iad 6y ago
      The `--reference` and `--dissociate` flags to `git clone` can be used to avoid the majority of the network transfer while still creating an independent local repository.
    • jayd16 6y ago
      Like I said, I'd usually just clone locally, as in clone from the repo you already have on disk.
  • e28eta 6y ago
    Maybe too obvious, but if you’re not pushing everything to the remote, local-only content is available in both worktrees.
• monocularvision 6y ago
  “Let me share the Good News of git worktrees” is a thing I say often in our work Slack.