Concept and mechanism
Issues record work and problems; PRs propose changes; Discussions support exploring questions and options without immediately assuming a closable task. Link a change to its problem so APS, development, and management can find the same decision. Closing keywords in a PR description depend on targeting the default branch; merging into another branch does not meet that condition. A simple numeric reference likewise does not mean execution or acceptance. Templates help collect consistent context, impact, and reproduction details. Assignees, labels, and filters support routing but need criteria understood by the team. A closed issue is a record state rather than automatic proof of service recovery.
Guided application
In fictional handover, replace scattered message chains with a summary linking to authorized evidence. Match notifications to responsibility to reduce noise without losing review requests. Gists suit small examples, but secret means unlisted rather than private: anyone obtaining the URL can read it. Never use absence from search as a control for restricted logs. Wikis support longer documentation; Pages publishes static sites and has its own visibility. In Enterprise Cloud without EMU, a project site can be public even with a private repository. Confirm effective site access before publishing internal documentation. The selected channel should match classification and recipients rather than convenience alone.
Closes #42 in a PR to release-candidate does not have the same effect as a PR to the default branch.
Common pitfalls
Mention as closure; closed issue as recovered service; secret gist as private; private repository as private site.
Related topics: Git, local state, and collaboration · Repositories, guidance files, and maintenance · Automation, development environments, and AI
Keep problem, change, evidence, and audience connected in the workflow.
Reference: PR issue linkage and default branch · GH-900 skills measured January2026;study guide updated2026-02-19