2 ms·
Branch? Fork? With a decent DVCS, they're the same. Did you just clone your team's repository in order to work on it? Congratulations, you just forked. Even a
by rlpb 14y ago
Branch? Fork? With a decent DVCS, they're the same.
Did you just clone your team's repository in order to work on it? Congratulations, you just forked. Even a checkout from a non-DVCS like svn is really a fork, if you think about it.
The best tooling passes this equivalence all the way to the user. git does an excellent job of it.
Then all you have left are semantics and namespacing.
- varsketiz 14y agoThat is very spot on. However, forking downsides are very real - more repositories to maintain, which results in harder to setup infrastructure (kicking off builds of 30 repositories is more work to setup than kicking off builds of branches in 1 repository). Installing webhooks or server-side hooks is also a bigger pain in a fork network.
- rlpb 14y ago> kicking off builds of 30 repositories is more work to setup than kicking off builds of branches in 1 repository In git, just pull them all into one repository. It's trivial, provided that you are able to list the repositories and branch names (which is a namespacing problem).