Team Saved Replies

GitHub's saved replies are personal. Everyone on a team ends up writing their own version of the same answer, and they drift apart. Team Saved Replies fixes that by keeping the templates in a markdown file in a repository you already have. Anyone who can read that file gets the same replies, and when someone improves one, everyone picks it up on the next refresh. HOW IT WORKS Write templates in a markdown file: a heading for the name, a fenced code block for the reply. Commit it. Point the extension at that file's page on GitHub. That is the whole setup. WHERE THE TEMPLATES SHOW UP - In GitHub's own saved replies dialog, alongside your personal ones, on issues and pull requests. - In the extension popup, as a searchable list you can copy from. - In a side panel, with what you used recently at the top, grouped by repository. - Behind a tab on the edge of the GitHub page, which opens the side panel. - Inline as you type. Type ! at the start of a word in any comment box and a filtered list appears at the cursor. Keep typing to narrow it, press Enter to insert. The list is ordered by what you use most, so the reply you reach for daily is usually the first one. The trigger can be changed or switched off. CONFIGURING IT Add as many template files as you like. Each one can apply to all of GitHub or be limited to a single organisation, and to issues, pull requests, or both. So a source for your own organisation and one for an open source project you maintain can sit side by side without getting in each other's way. Templates are re-fetched on a schedule you choose, and you can sync any source by hand to check a URL works. PRIVACY Nothing is collected and nothing is sent anywhere. Your sources and the cached templates stay in your browser's local storage. The only network request the extension makes is to the GitHub page you configured, using your own GitHub session, which is why private repositories work if you can already read them.