1. Keep github.com separate from Copilot CLI voice
GitHub’s website has editable surfaces for issue titles and bodies, pull-request descriptions, discussion posts, ordinary comments, line comments, and review summaries. Current GitHub web documentation describes text and Markdown controls for those surfaces, not one shared website microphone workflow.
GitHub Copilot CLI is different. Its native `/voice` command records at an interactive terminal prompt and GitHub documents local transcription there. Do not transfer the CLI shortcut, language models, `/refine` command, or local-audio claim onto github.com.
2. Dictate only after the intended editor has focus
Open the correct repository, issue, pull request, or discussion. Place the insertion point in the exact editable field, then start the current macOS Dictation shortcut. Speak, stop Dictation, and confirm that the transcript appeared in that field rather than a search box, command palette, or another browser tab.
For a new issue, keep the title and body separate. GitHub’s current issue procedure ends with Submit new issue; voice input should create reviewable field text, not choose the repository, issue type, assignee, labels, project, milestone, or final submission for you.
- Confirm the repository and destination before speaking.
- Focus the exact title, body, comment, or review field.
- Stop Dictation before navigating or submitting.
3. Use Write and Preview as an accuracy check
GitHub says every comment field has a formatting toolbar and supports GitHub Flavored Markdown. Dictated prose can work well for context, reproduction steps, expected behavior, review rationale, and discussion replies, but exact Markdown, inline code, tables, task lists, URLs, and identifiers still need inspection.
Use the Preview tab before publishing a long issue or pull-request description. GitHub documents Command + Shift + P on Mac for toggling Write and Preview in comments and issue or pull-request editors. A clean transcript can still render incorrectly when punctuation changes a link, mention, task list, or code span.
4. Treat comment and review submission as consequential actions
GitHub documents Command + Enter on Mac as the shortcut that submits a comment. It also documents Command + Shift + Enter for submitting a review comment from Files changed. Keep those shortcuts separate from the Dictation shortcut and do not press them until the complete draft is visible.
A pull-request review has more state than an ordinary comment. Pending line comments can remain visible only to you until the review is submitted, and the final review can be Comment, Approve, or Request changes. Confirm the intended state and review summary before Submit review.
5. Review the details speech recognition is likely to damage
Check repository and issue references, usernames, @mentions, branch names, file paths, function names, package names, version numbers, negations, security language, and reproduction steps. Read exact code and commands from a trusted source rather than speaking them from memory.
For a bug report, verify the observed behavior, expected behavior, minimal reproduction, environment, logs, and impact. For a review, verify whether a statement is a question, a suggestion, a blocking concern, or a reason to approve or request changes.
6. Troubleshoot the input layer before changing GitHub settings
If Dictation fails everywhere, test one short sentence in TextEdit and follow Apple’s current checks for Keyboard settings, shortcut, language, microphone, Voice Control, and network requirements. If TextEdit works, system recognition is functioning.
If only github.com fails, confirm the field is editable and that focus is still inside it. Website microphone permission belongs to a site feature that directly captures audio; system Dictation is a separate Mac input path. Also check GitHub’s current page shortcuts so a character or modifier key is not navigating, previewing, or submitting unexpectedly.
7. Add IraVoice only for a distinct local or structured workflow
Use macOS Dictation first for occasional GitHub prose. Use Copilot CLI `/voice` first when the destination is already an interactive Copilot prompt.
IraVoice 0.7.1 is the separate option for macOS 26+ Apple-silicon Macs when recognition and supported formatting should run on the Mac across supported apps, or when a longer spoken requirement should become reviewable Markdown before you choose GitHub, Jira, or an agent. IraVoice does not sign in to GitHub, read repository context, select an issue or pull request, add mentions, choose a review status, press Submit, or merge code.