How to Dictate GitHub Issues and PR Reviews
Quick answer: To dictate GitHub issues or pull request reviews, focus the GitHub text field, hold your Hold to Talk shortcut, speak the full issue, PR note, or review comment, release, then review the pasted text before submitting.
What happens after install
See the demo- Focus any Mac text field.Cursor, ChatGPT, Slack, email, docs, terminals, browser forms, and more.
- Hold the shortcut and speak.Use Fn/Globe or a custom hotkey only while you are talking.
- Release to paste.The transcript appears in the active app instead of a separate dictation workspace.
- Review before sending.Hold to Talk never auto-submits prompts, messages, emails, or commands.
GitHub writing is often too detailed for quick typing. Good issues include reproduction steps, expected behavior, screenshots or logs, priority, and the context someone needs to act. Good pull request reviews explain risk, intent, and the specific change you want. Hold to Talk lets you speak that context directly into the GitHub field you already have focused.
Best GitHub fields for voice dictation
- Issue descriptions: symptoms, reproduction steps, environment details, and expected behavior.
- Pull request descriptions: what changed, why it changed, testing notes, and rollout risk.
- Review comments: specific concerns, suggested alternatives, and questions for the author.
- Discussion replies: longer technical context that would be slow to type.
Issue template to speak
We are seeing the checkout success page show the old subscription state after Stripe returns success. Steps to reproduce: start from a free account, click upgrade, complete checkout, then land back on success. Expected behavior is that the Pro state appears without a manual refresh. Please inspect the webhook event, the local billing cache, and the success page query.
That level of detail is useful, but most people shorten it when typing. Voice makes the complete bug report cheaper to write.
Pull request review structure
| Review part | What to say |
|---|---|
| Observation | Name the behavior, file, or code path you are reviewing. |
| Risk | Explain the bug, maintenance cost, regression risk, or user impact. |
| Suggested fix | Ask for a specific test, guard, copy change, or smaller implementation. |
| Tone | Keep the comment direct, specific, and about the code. |
Review before submitting
Hold to Talk pastes a draft. It does not submit the GitHub form. Read the pasted text before posting, especially if the comment mentions credentials, production data, customer names, security issues, or a teammate's work.
Useful custom vocabulary
Add repo names, feature flags, internal service names, acronyms, and common file paths to custom vocabulary. That makes dictated GitHub text cleaner and reduces edits before submitting.
FAQ
Can Hold to Talk type into GitHub?
Yes. Hold to Talk pastes text into the active Mac text field, so it can be used in GitHub issues, pull requests, comments, and review boxes.
Does Hold to Talk submit the GitHub comment automatically?
No. It pastes the dictated text so you can review and edit before clicking Comment, Submit review, or Create issue.
What GitHub writing is best for dictation?
Bug reports, reproduction steps, pull request summaries, review comments, and technical discussion replies are good fits because they benefit from context.
Try Hold to Talk on Mac. Start with the free plan, then upgrade only if it fits your daily workflow.
Download Hold to Talk Watch the 8-second demo