The cursor blinked, waiting for you to decide.
You just ran git checkout -b new-feature and opened a file. Vim stared back at you, green on black. You didn’t mean to be here, but here you are. Your terminal is frozen in time until you remember the keys that feel more like a spell than a command.
Esc :q! and you’re free. Or maybe not — because now you’re wondering why Vim appears when switching branches with Git, and how to move faster without losing focus.
When running git checkout or git switch, Git may trigger Vim to handle commit messages, merge conflicts, or rebase steps. It’s the default text editor for Git in many environments. If you installed Git on a Unix system or through most Linux package managers, Vim likely came with it. Unless you explicitly changed your Git editor settings, Vim is what you get.
This isn’t a bad thing. Vim is fast, lightweight, and everywhere. Knowing the basics saves you from confusion when Git calls it into action.
Common Git + Vim Workflows
- Editing commit messages
After git commit without -m, Vim opens so you can write a detailed message. Use i to insert text, Esc to stop editing, then :wq to save and quit. - Resolving merge conflicts
Run git mergetool, and Vim (or sometimes vimdiff) launches with all changes side by side. Navigate with ]c and [c, choose changes, save, and continue. - Interactive rebases
git rebase -i drops you into Vim with a list of commits. Change pick to squash, reword, or edit as needed, then finish the rebase. - Changing branches mid-edit
If git checkout detects unmerged changes, it might create a stop point in Vim so you can decide whether to keep, stash, or discard.
If you never want to see Vim here, set a different editor:
git config --global core.editor "nano"
Or stick with Vim but customize it:
git config --global core.editor "vim"
Adding .vimrc tweaks can improve your Git editing sessions — line numbers, syntax highlighting, and better diff views make a difference.
Speed Matters
Every pause in a workflow is a potential break in momentum. When Git and Vim meet, you either know what to do, or you stop to search commands. Learn them now. Even if you later switch editors, that quick literacy pays off in speed and confidence.
You can also see what it’s like to move from command to change without friction. With the right tooling, the step from edit to deploy takes minutes instead of hours. That’s why platforms like hoop.dev exist — to strip out the waiting and let you see your code live almost instantly. Try it, and the next time Git blinks and Vim stares, you’ll already be a step ahead.