> Is there any best practice for a large team of 50 developers to work in Git? Think about how the Linux kernel works. A single person at the top who has fina

> Is there any best practice for a large team of 50 developers to work in Git? Think about how the Linux kernel works. A single person at the top who has final say in the final product, a lieutenant responsible for each smaller group working on one subsystem. Insist on keeping your history clean. Good commit messages and comprehensible changesets are necessary to make sure the code is understandable by code review, future maintainers, and when different teams' code needs to interoperate.