Source control has less to do with the VCS system you use, and more to do with the stages code goes through on the journey from inside a developer's head, tested and merged into the main line, deployed to production, and thence in time to being identified as that accursed legacy system that is causing all the problems.
At Truss, most of our projects will use Git as their VCS, and usually with GitHub as the host for their repositories, but this is not a hard and fast rule (clients will often host their own repositories in their own system).
This page provides a summary of tools we commonly use for source control
📄️ Git Repos
This page provides guidance on how to set up and manage your Git repos.
📄️ Git Workflow
At Truss, we've tried to come up with some standardized workflows for
📄️ Master to Main branch rename
These instructions will help moving repos from using the default branch name master and modify it to be
- Dangit, Git! - A plain English guide to solving common Git issues