3 ms·
That is very spot on. However, forking downsides are very real - more repositories to maintain, which results in harder to setup infrastructure (kicking off bui
by varsketiz 14y ago
That 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).