Welcome to Team Workflows, the sixth module of the course. You now know the mechanics of branches, remotes, and pull requests — but working on a team is less about new commands and more about shared conventions. When several people push to the same repository every day, the difference between a smooth project and a chaotic one comes down to agreements: which branches exist and why, what a good commit message looks like, how you stay out of each other’s way, and how a finished version becomes a labeled release.

You’ll start by comparing branching strategies — GitHub Flow, Git Flow, and trunk-based development — and learn which fits which kind of team. Then you’ll adopt Conventional Commits, a simple format that makes history readable and even automatable. You’ll pick up the habits that let people work together without stepping on each other, and you’ll learn tags and releases with semantic versioning so every shipped version has a name you can return to. The module closes with a guided project that runs a full feature → pull request → release cycle.

Every Git command here was run for real; the GitHub steps are shown exactly as you’ll perform them. Start with Lesson 1 on branching strategies.