Start here · Essential guide
Version Control Explained for Engineers
What version control is, why technical teams rely on it, and the core ideas of history, commits, branches and collaboration, explained without jargon.
Software Practice
Version Control
Tracking changes, branching and collaborating on shared files.
Branching Strategies for Small Teams
Compare common ways to organise Git branches, from a single shared branch to feature branches and release branches, and pick one that suits a small team.
Git Basics: Commits, Branches and Merges
A step-by-step walk through the everyday Git workflow: staging changes, committing, creating a branch and merging it back, with the commands explained.
How to Write Useful Commit Messages
Habits for short, descriptive commit messages: a clear summary line, a body that explains why, and consistent conventions that keep project history readable.
Resolving Merge Conflicts Calmly
Why Git merge conflicts happen, how to read conflict markers, and a careful step-by-step routine for resolving them without losing anyone's work.
Tagging Releases and Keeping a Changelog
How to mark released versions with Git tags and keep a changelog that tells users and teammates what changed between releases, with simple examples.
Undoing Mistakes in Git Safely
How to discard edits, recover a deleted file, revert a bad commit and rewrite local history in Git, with guidance on what is safe once work is shared.
Version Control for CAD Files and Other Binary Data
Why drawings, models and other non-text files are hard to track, and general approaches such as locking, naming rules, large-file tools and PDM systems.
What a Pull Request Is and How to Open a Good One
What a pull request is, why teams use it, and how to write a clear title, description and small change set so reviewers can understand and act quickly.
Related topics