How to understand GitHub saved replies
Speed up issue triage and bug feedback with GitHub saved replies. Create reusable comment templates for bug reproduction requests and common PR reviews.
What this covers
Saved replies cut repetitive typing when you answer the same kinds of issues and pull requests. This page is the conceptual overview from About saved replies; the create / edit / delete / use flows live in the sibling how-tos.
flowchart LR
Settings["User Account Settings -> Saved Replies"] --> Create["Define Title & Template Content"]
Create --> Comment["Open Issue or PR Comment Box"]
Comment --> Insert["Select Saved Reply or Press Ctrl+."]How saved replies work
- You author a title plus body once under your account Settings.
- The reply is yours personally, not per repository.
- After it exists, you can insert it while commenting on issues, pull requests, and discussions in any repository or organization you can comment in.
- Maximum: 100 saved replies. At the limit, delete unused ones or edit existing replies.
Built-in duplicate reply
GitHub provides a Duplicate issue saved reply you can use to mark an issue as a duplicate and point at a similar issue.
Where to go next
FAQ
How do I quickly insert a saved reply into a GitHub issue or pull request comment?
Press Ctrl + . (or Cmd + . on Mac) inside any GitHub comment box to bring up your saved reply menu. Saved replies insert pre-written snippets instantly without opening settings.