Pin and Lock GitHub Discussions
Pin a discussion when it should remain discoverable and close or lock conversation only for a clear maintenance reason. Discoverability, resolution and moderation are different decisions.
Step-by-step guide
Check access and scope
You need suitable discussion management or moderation permissions. Explain the rule and keep a path for legitimate follow-up questions.
Find the authoritative decision
Identify the authoritative decision or community instruction.
Write an outcome summary
Summarize the outcome at the top of the discussion.
- Worked example: Pin an explanation of invitation expiry behavior with links to current documentation. If an old debate is closed, point readers to the accepted decision and a suitable channel for new evidence.
Pin for discoverability
Use the available pin controls for the relevant audience.
Close or moderate deliberately
Close resolved discussions or apply locking through moderation controls when justified.
Link the follow-up path
Link the next place for follow-up and review stale pinned material.
Verify the result
Readers can find the current decision and understand whether discussion is still open and where to raise new information.
Common mistakes
Check the handoff edge case
Locking a discussion without explaining the next support path can suppress legitimate new evidence. Provide an appropriate route for follow-up.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.