Most organisations with a collaborative wiki have some sort of "tips and tricks" page, where users can freely add or update advice for everyone to use. It appears the CIA is no different, with the recent "Vault 7" dump from WikiLeaks revealing the US intelligence service's closely guarded collection of Git cheats. What's surprising is a few are actually useful.
For small-medium software companies, scaling is usually not a problem. Microsoft, however, doesn't have that luxury. For instance, the developer is an enthusiastic user of Git, with many of its projects available on GitHub including .NET Core, the Chakra Javascript engine and Visual Studio Code. When it comes to the Windows source... Git doesn't scale and so, Microsoft was forced to create its own virtual file system for Git -- which it's just open-sourced -- to streamline repo operations.
GitHub has been slowly and steadily improving its platform. Just this year it's introduced browser file uploads, commit "reactions" and user blocking. These were nice, but didn't add much to the service's appeal. Unlimited private repositories however? That's not bad.
Writing concise, yet descriptive commit messages for version control is a difficult art to perfect. While you're on the path of getting those notes down to their efficient best, here are a few questions to ask yourself before doing that push.
