4.5. Reflection Checkpoint

Key Takeaways

• Issues track units of work, pull requests propose reviewable code changes with a real diff, and discussions hold open-ended conversation — pick the surface based on the shape of the conversation, not just its topic.
• A closing keyword (Closes #12) in a pull request only auto-closes the linked issue on merge, not on close-without-merge.
• Notifications are subscription-driven: watching a repository is one trigger, but @mentions, assignments, and thread participation notify you regardless of your watch setting.
• Gists, Wikis, and GitHub Pages each publish content differently — a standalone snippet, a repo-attached documentation space, and a public static site, respectively.

Connecting Forward

Phase 5 shifts from human-to-human collaboration to automation and AI: GitHub Actions, GitHub Copilot (including Agent Mode and multi-model support), and cloud development environments like Codespaces.

Self-Check Questions

• Why does GitHub tie the auto-close behavior specifically to merging a pull request, rather than to opening one?
• If a repository owner disables its Wiki entirely, what's the closest remaining option for hosting long-form documentation about that project?