Dictation in GitHub Issues on a Mac

Issue bodies are prose: what broke, what you expected, what you saw. Dictation is a good fit. The complication is that GitHub's comment box is wired to the rest of the platform, so two spoken characters have consequences outside the text.

The GitHub-specific trap: a dictated 'at' notifies someone

Typing "@" in an issue body opens the user-mention autocomplete. Say "at" while dictating an email address, a handle, or the phrase "at the same time", and the picker opens over your text. Worse, if the following dictated word happens to match a username and you press Return, GitHub inserts a real mention. Posting that mention sends a notification to a stranger who now has your bug report in their inbox.

• Press Escape to close the picker before continuing to dictate.
• Before you submit, scan the preview for blue @ links you did not intend. The preview tab renders mentions as links, which makes them easy to spot.
• The same applies to a dictated "hash" or "number sign", which opens the issue and pull request picker and can cross-link an unrelated issue.

The second trap: Command+Return submits

Command+Return posts the comment. A dictation hotkey built on Command can submit a half-dictated issue to a public repository. Bind dictation to a key that does not involve Command, or draft in a scratch file and paste.

Dictate an issue

1. Turn Dictation on once: System Settings → Keyboard → Dictation. Full steps in enable dictation on macOS.
2. Open the new issue form and click into the body field. The title is a separate field and takes no spoken navigation.
3. Dictate the prose in one pass, using the structure below.
4. Stop, then type the parts speech gets wrong: file paths, identifiers, version strings, and anything that belongs in a code fence.
5. Open the Preview tab and read it before submitting.

A structure that dictates cleanly

Dictation rewards a shape you can hold in your head while talking. This one has no formatting until the editing pass:

1. One sentence saying what broke.
2. The steps, spoken as a sequence: first, then, then.
3. What you expected, then what actually happened. Two sentences.
4. The environment: OS version, app version, browser.
5. What you already ruled out. This is the part reviewers value most and the part people skip when typing.

If nothing types at all

• GitHub runs in a browser, so the microphone permission belongs to the browser and to the dictation tool, under System Settings → Privacy & Security → Microphone.
• If focus leaves the comment box, GitHub's own single-key shortcuts take over and dictated letters start triggering navigation.
• Dictation dead everywhere, not just GitHub: dictation not working on Mac.

One hotkey across the editor and the browser

Voice Type inserts the finished text on release rather than streaming keystrokes, so the mention and issue pickers never open mid-sentence, and the same hotkey works in the editor where you found the bug: voice typing for Mac.

Keep going

• Dictating pull request descriptions on GitHub
• Dictation in Linear (the slash menu and the draft that saves on Escape)
• Voice typing in VS Code

Sources

• GitHub Docs: Basic writing and formatting syntax
• GitHub Docs: Keyboard shortcuts
• Apple: Dictate messages and documents on Mac