Dictate in any app · Code

Voice typing in GitKraken

A visual git client makes branching obvious and commit messages no easier to write. Typally works at the keyboard level, so anywhere GitKraken accepts typing, it accepts your voice instead.

We make Typally, so treat this as a vendor's guide. Where GitKraken has a built-in option we say so, including when it is the better choice.
Dictate into GitKraken Free on Windows and macOS. No payment details needed to start.
Try Typally free

In short

  • GitKraken's own dictation: None. The commit message box is a plain text field.
  • What Typally does instead: types into the focused window, so it works in GitKraken and everywhere else you write.
  • Best used for: commit message summaries and bodies

Does GitKraken have built-in dictation?

None. The commit message box is a plain text field.

Why dictate in GitKraken at all?

GitKraken removes the friction from staging, branching and merging, which leaves the commit message as the slowest part of committing. So it stays one line, and the history stays useless.

In practice people use it for: Commit message summaries and bodies, pull request descriptions, and issue comments through its integrations.

How to dictate in GitKraken

Typally runs in the background and types into whatever window has focus, so there is nothing to install inside GitKraken:

1

Get Typally running

Install, sign in, and it waits in the tray.

2

Focus the GitKraken field you want the words in

Put the cursor in the field you are about to fill — GitKraken decides where the text lands, not Typally.

3

Speak with the key held down

Push to talk, say your piece, release to transcribe.

4

Read it before you move on

The summary and body are separate fields. Click into the body before dictating anything longer than a line.

What Typally adds in GitKraken

Typally types into the commit body field so writing a real explanation costs about as long as saying it. Custom vocabulary keeps branch, service and module names intact, which matters in a message that will be read by grep as often as by a person.

What this looks like in practice

A developer starts speaking a two-sentence body on every non-trivial commit. When a regression appears months later, git log explains the reasoning instead of listing 'fix' twelve times.

One habit that makes it work better

Use the message body, not just the summary line. The summary says what changed; the body is where why lives, and why is what git log is for.

What to watch out for in GitKraken

The summary and body are separate fields. Click into the body before dictating anything longer than a line.

Frequently asked questions

Does GitKraken have dictation?

No. Its message fields are plain text inputs.

Should commit messages have a body?

For anything non-trivial, yes. The summary is a headline; the body is the explanation.

Can I dictate pull request descriptions in GitKraken?

Yes, wherever it gives you a text field.

Try it in GitKraken

Start on the free plan (100 minutes a month, no card). Pro lifts the cap and adds meeting notes for $7.99/month.

Try Typally free

Also dictate in: Sourcetree · GitHub · GitLab · NetBeans · iTerm2 · see all apps