Voice to Text for Sourcetree
Sourcetree makes Git visual, but writing about your changes still takes forever. Commit messages, branch names, stash descriptions, tag annotations. All that context your repository needs to make sense six months from now. Blurt lets you speak it instead of typing it. Hold a button, describe your changes naturally, release. Text appears in Sourcetree wherever your cursor is. Your commits get meaningful messages. Your branches have names that actually describe the work. Your stashes stop being mysterious piles of uncommitted code.
The Typing Problem
Commit messages that say anything useful take too long to type
You just finished a fix that touched eight files. You know exactly what you did and why. But typing out 'Refactored authentication middleware to handle expired JWT tokens gracefully, added retry logic for network failures, updated error messages to be more user-friendly' takes forever. So you write 'fix auth' and move on. Three months later, you're debugging and your commit history tells you nothing.
Branch names become meaningless abbreviations
You're starting a new feature. You should name the branch something descriptive like 'feature/user-profile-image-upload-with-cropping'. But typing that is tedious, so you create 'feat/img-upload' instead. Now your branch list is full of cryptic abbreviations that nobody understands without checking the actual code.
Stash descriptions are always empty
You need to context switch and stash your current work. Sourcetree asks for a description. You skip it because typing takes time. Two weeks later, you have five stashes and no idea what any of them contain. You pop each one, check the changes, decide it's not the right one, stash again. A task that should take seconds takes ten minutes.
Tag annotations never get written
You're tagging a release. You should document what's in this version: major features, breaking changes, migration notes. But after a day of coding and testing, you just want to ship. So you create a lightweight tag with no annotation. Your release history becomes a list of version numbers with no context about what actually changed.
Interactive rebasing becomes a chore
You're cleaning up commits before pushing. Each commit message could use improvement, but rewriting them in the text editor is slow. You leave the messages as-is, pushing 'WIP', 'fix', 'more fixes' into your main branch. Your Git history becomes a mess of meaningless messages that help no one.
How It Works
Blurt works everywhere in Sourcetree. Commit message boxes, branch name fields, stash descriptions, tag annotations, any text field. If you can type it, you can speak it.
Hold your hotkey
Press your chosen shortcut while your cursor is in any Sourcetree text field. A small indicator shows Blurt is listening.
Describe your changes naturally
Explain what you did, why you did it, what the branch is for. Talk like you're explaining to a colleague. Blurt handles punctuation automatically.
Release and done
Text appears in Sourcetree. Edit if needed, or commit directly. Your thoughts become Git history in seconds, not minutes.
Real Scenarios
Writing commit messages that future you will thank you for
You just finished refactoring the payment processing module. Hold the button and describe: 'Refactored payment processing to use the new Stripe API. Replaced deprecated charge methods with PaymentIntents. Added proper error handling for declined cards and network timeouts. Updated webhook handlers to process the new event format. Migration note: run the database migration before deploying to update the transactions table schema.' A commit message that captures everything. Six months from now, when something breaks, you'll know exactly what this commit changed.
Creating branch names that describe the actual work
You're starting work on a new feature. Hold and speak: 'feature slash user notification preferences with email and push options.' Blurt transcribes it, you adjust the formatting to 'feature/user-notification-preferences-email-push-options'. A descriptive branch name in seconds. Your team knows what you're working on just by looking at the branch list.
Stash descriptions that save you from future confusion
You need to switch branches but have uncommitted work. Hold and describe: 'Work in progress on the dashboard redesign. Charts are working but the date picker still needs the range selection feature. Also started on the export to CSV button but it is not wired up yet.' Now when you come back in two weeks, you know exactly what state this work was in and what still needs doing.
Tag annotations that document releases properly
You're tagging version 2.4.0 for release. Hold and speak: 'Version 2.4.0 adds the team collaboration features including shared workspaces, real-time presence indicators, and collaborative editing. Breaking change: the workspace API now requires authentication. Migration: existing users need to run the workspace migration script before accessing shared features.' Your release tags become actual documentation.
Amending commits with better messages
You just committed with a lazy message and immediately regretted it. Before pushing, you can amend. Hold and speak: 'Fixed the race condition in the websocket connection handler that was causing duplicate messages when clients reconnected rapidly. Added a connection ID check and debounce logic to prevent the double-send issue.' Amend the commit with a message that actually explains what you fixed.
Writing merge commit messages with context
You're merging a feature branch. Sourcetree offers a default message but you want to add context. Hold and explain: 'Merged the new search functionality. This adds full-text search using Elasticsearch, search result highlighting, and search analytics tracking. The search index builds automatically on first run but takes about 10 minutes for large datasets.' Merge commits that explain what just got merged.
Documenting complex rebases
You're squashing several commits into one before pushing. Hold and summarize: 'Consolidated the authentication overhaul commits. This changeset replaces the session-based auth with JWT tokens, adds refresh token rotation, implements secure cookie storage, and updates all API endpoints to validate tokens. Tests have been updated and all pass.' Clean history with meaningful messages.
Why Sourcetree users choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Click microphone or double-tap function key |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Technical terms | Handles Git terminology (commit, rebase, merge, stash) | Often mishears technical vocabulary |
| Reliability | Consistent accuracy in native app text fields | Sometimes unreliable in desktop apps |
| Price | $10/month or $99/year, free tier included | Free but limited |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt