Create Saved Replies in GitHub
Create saved replies for recurring triage questions, then adapt each reply before posting. A reusable response should reduce repetition without implying that a maintainer reviewed evidence they have not read.
Step-by-step guide
Check access and scope
Saved replies are managed in your account settings. Review repository contribution guidelines before drafting shared triage language.
Open Saved replies
Open account Settings and Saved replies. Open account Settings > Saved replies, add a title and body, then use Preview before saving.
Name the triage situation
Create a descriptive title for the specific triage situation.
- Worked example: For an expired-invitation report, ask for the safe reproduction steps, expected behavior and product version. Explicitly tell the reporter not to post tokens or personal details in public.
Write a focused request
Write a concise request with the evidence needed next.
Preview rendered content
Preview Markdown and links.
Tailor the draft response
Insert the reply into a draft response and tailor it to the actual report.
Verify the result
The saved reply renders correctly and the tailored response asks for relevant information without requesting secrets.
Common mistakes
Check the handoff edge case
Requesting tokens or identifiable customer data in a public response can create a new problem. Ask for safe reproduction information instead.
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.