4 ms·
This is pretty cool. Although, on large codebases a la facebook or google size, I would think having a copy of the repo per branch might be intractable - also,
by nartz 9y ago
This is pretty cool. Although, on large codebases a la facebook or google size, I would think having a copy of the repo per branch might be intractable - also, somewhat unnecessary since one can just switch branches...
- deleted 9y ago[deleted]
- oneeyedpigeon 9y agoThe trouble with 'just switching branches' is that it quickly gets very complicated, if not impossible, without either checking in incomplete code or stashing it.
- nartz 9y agoIs stashing an issue?
- QasimK 9y ago[git-worktree](https://git-scm.com/docs/git-worktree https://git-scm.com/docs/git-worktree) allows you to have "copies" of the repo cheaply. This can be useful when switching branches would have a high overhead, for example you need to reconfigure your local environment (database, dependencies, etc.).