Absolutely—this is a fantastic choice, especially given your daily workflow! Since you’re already using VS Code as your go-to editor for Django and Python development, setting it as Git’s default editor will make your work far more seamless, and it’ll lower the learning curve as a first-time Git user. Here’s why this makes sense:

• Familiarity cuts down on friction
  You already know your way around VS Code’s interface, shortcuts, and editing tools. Instead of fumbling with Nano’s terminal-specific commands (like remembering Ctrl+O to save or Ctrl+X to exit—easy to mix up when you’re new!), you’ll handle Git’s text tasks (writing commit messages, editing rebase files, etc.) in an environment you’re comfortable with. This lets you focus on learning Git itself, not a new editor.

• Better tools for Git-related editing
  VS Code offers perks that light terminal editors like Nano don’t: syntax highlighting for Git-specific files (like rebase todo lists), built-in spell check, and even extensions (like GitLens) that boost your Git workflow. These small touches make it easier to write clear, well-formatted commit messages—something crucial for keeping your project history organized.

• Seamless workflow integration
  VS Code already has robust built-in Git support (you can commit, pull, push, and resolve conflicts right in the editor). Setting it as your default editor ties this together perfectly: when Git needs you to input text (e.g., running git commit without the -m flag, or git rebase -i), it’ll open the relevant file directly in VS Code. Save and close the window, and Git will pick up right where it left off—no switching between terminal and editor mid-task.

How to set it up #

It’s a quick terminal command:

git config --global core.editor "code --wait"

The --global flag makes this setting apply to all your Git repositories, and --wait tells Git to pause until you close the VS Code window (without this, Git might think you’re done editing before you’ve saved!).

If you ever want to switch back to Nano later, just run:

git config --global --unset core.editor

This will revert Git to its default editor (usually Nano).

At the end of the day, the best Git editor is the one you’re most comfortable using. For a beginner already invested in VS Code for Python/Django work, this is a no-brainer—it’ll help you build confidence with Git faster while keeping your workflow consistent.

内容的提问来源于stack exchange，提问作者Shane S