The Git checkout command runs. Vim opens without warning. Your cursor blinks in a file you didn’t expect to edit.
This is the moment most developers hit escape, type :q!, and swear. It’s not a bug. It’s Git using Vim as the default editor for tasks like resolving conflicts, editing commit messages, or rewriting history.
Understanding why Git triggers Vim is simple: whenever git checkout engages an interactive process—like switching branches with unfinished merges—it can drop you into the core editor set in your $EDITOR environment variable. For many systems, that editor is Vim.
To change it, run:
git config --global core.editor nano
Or swap nano for any other editor you prefer: code, emacs, sublime, etc. If you want to completely bypass the editor during operations, you can pass flags like:
git checkout branch-name --no-edit
However, knowing a few Vim basics can save time when you are stuck mid-process. Press i to insert, Esc to escape, :wq to write and quit, :q! to quit without saving. Git will continue once Vim closes.
If you work in fast-moving environments, friction in commands kills flow. Configuring Git so you control when Vim appears keeps your focus on the branch switch, the merge, or the hotfix—without detours into buffer navigation.
Stop letting the editor choose your path. Configure Git once and keep your workflow tight. Try it live in minutes at hoop.dev and see how smooth your branch changes can be.