References: Pull requests

Primary sources

Pro Git by Scott Chacon and Ben Straub. Chapter 6 (GitHub) covers the PR mechanic on GitHub. Licensed under Creative Commons Attribution Non Commercial Share Alike 3.0 Unported.

Read online at git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project and git-scm.com/book/en/v2/GitHub-Maintaining-a-Project.

GitHub Docs, About pull requests at docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests. The canonical reference for the GitHub PR UI. Licensed under Creative Commons Attribution 4.0.

Secondary sources

Atlassian Git Tutorials, “Making a Pull Request” section at atlassian.com/git/tutorials/making-a-pull-request. Licensed under Creative Commons Attribution 2.5 Australia.

Atlassian’s GitFlow workflow article (atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) provides additional context on how PRs fit into team workflows.

Further reading

On writing good PR descriptions: the Conventional Commits spec covers commit-message conventions that also apply to PR titles in squash workflows. (Referenced in L3 as well.)

On code review etiquette: Google’s engineering practices documentation on code review is widely considered the canonical reference. Some sections (like “How to do a code review”) are directly applicable to small teams; others (like author/reviewer SLA) assume Google’s scale.

On merge strategies: Atlassian’s article on merging vs rebasing covers the tradeoffs in more depth than L6 does. We’ll revisit in L12.

On PR templates: GitHub’s documentation on PR templates covers how to add a .github/PULL_REQUEST_TEMPLATE.md that pre-fills the canonical structure.

What this lesson does not cite

L6 does not yet cite specific open-source review cultures (Linux kernel, LLVM, etc.). These are interesting case studies for L9 / L10 but L6 stays at the team level.

L6 also does not cite specific company engineering blog posts (Stripe’s review culture, Etsy’s PR practices). The patterns in L6 are the consensus across these sources; citing each individually would bloat the references without adding pedagogical value.

License of this lesson

This lesson is part of the Clawdemy curriculum, licensed under Creative Commons Attribution NonCommercial Share Alike 4.0 International. Pro Git’s CC BY-NC-SA 3.0 license and Clawdemy’s CC BY-NC-SA 4.0 license are directly aligned (the 4.0 license is an approved compatible adaptation license for 3.0 source material per the 3.0 license’s later-versions provision). Commercial use is licensed separately at /legal/licensing.