The GitHub mechanisms that turn a repository into a place a team collaborates safely — forking, branch protection, code ownership, project planning, documentation, and shipping versions.
6 topics
Git gives you the version control; GitHub is where a team agrees on how to use it together. This chapter covers the collaboration layer: how outside contributors propose changes without write access, how a team makes review and passing checks non-negotiable before code reaches a protected branch, and how ownership of the codebase is encoded so the right people are pulled into the right changes.
The back half moves from gatekeeping to running the project: planning work alongside the code in Projects, documenting it on the surface that fits its cadence, and shipping versions as tags, releases, and packages. None of these are Git features — they are GitHub mechanisms layered on top of it, and together they are what separates a repository you push to from a repository a team can trust.
Collaboration controls, from top layer down to foundation