> For the complete documentation index, see [llms.txt](https://wiki.owain.codes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.owain.codes/git/command-line/making-vscode-your-git-editor-and-diff-tool.md).

# Making VSCode your Git editor and diff tool

To set Visual Studio Code as your default editor enter this command into command line:

`git config --global -e`

```
[user]
	email = your@email.com
	name = YourName
	signingKey = ""
[core]
	longpaths = true
	autocrlf = true
	safecrlf = warn
	editor = code --wait
[gpg]
	program = gpg
[commit]
	gpgSign = false
[tag]
	forceSignAnnotated = false

```

 By the way switch `--wait` holds shell until Visual Studio Code is closed. Make sure \[core] has the editor as code.

### Making VS Code your Diff Tool

To set Visual Studio Code as your `difftool`, you need to go into global git config file. Which you can access through previous mentioned command `git config --global -e`, then you need to add those entries (or replace existing ones).

```
[diff]
    tool = vscode
[difftool "vscode"]
    cmd = code --wait --diff $LOCAL $REMOTE
```

<https://blog.soltysiak.it/en/2017/01/set-visual-studio-code-as-default-git-editor-and-diff-tool/>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.owain.codes/git/command-line/making-vscode-your-git-editor-and-diff-tool.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.