Version Control Systems / Git
Collaboration
Shared remotes, review hygiene, and workflows—from trunk-based and GitHub Flow to Git Flow and monorepos.
Photo by Yosuke Ota on Unsplash
Collaborating with Git
Git stores history; teams add agreements on top—who merges, how branches are named, and how review happens before code reaches main. This overview maps those social layers to remotes, pull requests, and protected branches.
Code review and pull request hygiene
Good pull requests are small, test-backed, and easy to revert; good reviews focus on design and risk, not style nitpicks. Practices for authors and reviewers when Git history is shared on a protected main branch.
Git workflows for teams
Trunk-based development, Git Flow, and GitHub Flow compared—how branch lifetimes, release cadence, and CI maturity drive the model, plus scaling patterns for monorepos and open source.