3 ms·
I would put all projects under one repo as orphan branches. With some branch-naming conventions you can easily separate those.
by dr_win 10y ago
I would put all projects under one repo as orphan branches. With some branch-naming conventions you can easily separate those.
- postit 10y agoJust no.
- yosyp 10y agoImagine you just hired a new web developer, and added him to this repo. His first local repo clone will include 3 entire projects for iOS, Android, and backend server, that he has no use for, or should even have permissions to access in the first place. This sounds like a security nightmare, that also significantly impacts local update times and makes for a huge repo.
- vernon99 10y agoSo companies like Fb (with their gazillions of files) can afford a single repo and you hiring a new developer cannot?
- jacques_chester 10y agoI loathe orphan branches with an intensity that could produce a nation of orphaned children. My view is: unless you have an inescapable security, physical or performance reason not to have a single repo, have a single repo. Directories are for managing directories. Version branches are for managing versions. They are not the same thing.