Improving source control usage

There is more to source control than using good commits or having ensemble commits. Bad usage of source control is amplified when pairing remotely, thus it's even more important to respect some best practices.

Here is a list of the best practices I use for source control, which may already be familiar to you, in the form of a checklist:

• Use source control in any situation, no matter how small the project is.
• Add all resources to the source control (code, libraries, scripts, configuration, and so on).
• Check that your source control repository is functional before starting the project.
• Review the changeset before committing/pushing.
• Make sure newly added libraries are in the changeset as well.
• Only commit files that have meaningful changes (not non-behavioral changes such as spacing, alignment, styling, and so on).
• Use clear—ideally standardized—commit messages (start from the Linux kernel conventions...