Team Collaboration & Open Source Practices — Git & GitHub Fundamental…
The conventions that keep a shared history readable as a team scales
Steps in Team Collaboration & Open Source Practices
- Conventional Commits & Commit Message Standards — advanced · A structured commit message format that tooling and humans can both parse
- Semantic Versioning & Release Tagging — advanced · Version numbers that communicate the nature of a change, and tagging releases in Git
- Writing Changelogs — advanced · Communicating what changed in each release to users and other developers
- Contributing to Open Source Projects — advanced · Finding a project, understanding its contribution guidelines and submitting a real PR
- Git Etiquette & Team Norms — advanced · Unwritten rules that keep a shared repository pleasant to work in
- Handling Large Team Repositories at Scale — advanced · Keeping history, CI and reviews manageable as a repository and team grow
Part of
- Git & GitHub Fundamentals roadmap — the full learning path