Turn GitHub Discussions into Issues
Create a linked issue from a discussion once a concrete bug or deliverable is ready for ownership. Preserve the discussion as research context rather than copying every comment into the task.
Step-by-step guide
Check access and scope
You need the repository permissions required to create and maintain the issue. Decide which specific outcome is actionable before promoting the conversation.
Read the discussion evidence
Read the discussion and distinguish consensus from unresolved suggestions.
Define accepted scope
Write a concise problem statement and acceptance criteria.
- Worked example: A conversation about expired invitations can yield one issue for clearer recovery messaging while leaving configurable expiry policy as an open proposal. Avoid converting the entire debate into one oversized task.
Create the linked issue
Use the available create-issue action from the relevant discussion context. The discussion sidebar offers Create issue from discussion for users with triage permission; copied source text and labels still need editorial review.
Assign triage ownership
Link back to evidence and assign triage ownership.
Close the context loop
Post the issue link in the discussion and state what remains undecided.
Verify the result
The issue has an owner and testable outcome, and readers can trace it back to the original discussion.
Common mistakes
Check the handoff edge case
Automatically copied discussion text can contain unresolved proposals. Edit the issue into a clear actionable outcome before assigning work.
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.