git/contrib/vscode
Johannes Schindelin 12861e200a vscode: let cSpell work on commit messages, too
By default, the cSpell extension ignores all files under .git/. That
includes, unfortunately, COMMIT_EDITMSG, i.e. commit messages. However,
spell checking is *quite* useful when writing commit messages... And
since the user hardly ever opens any file inside .git (apart from commit
messages, the config, and sometimes interactive rebase's todo lists),
there is really not much harm in *not* ignoring .git/.

The default also ignores `node_modules/`, but that does not apply to
Git, so let's skip ignoring that, too.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-07-30 13:14:39 -07:00
..
.gitattributes contrib: add a script to initialize VS Code configuration 2018-07-30 13:14:38 -07:00
init.sh vscode: let cSpell work on commit messages, too 2018-07-30 13:14:39 -07:00
README.md contrib: add a script to initialize VS Code configuration 2018-07-30 13:14:38 -07:00

Configuration for VS Code

VS Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. Among other languages, it has support for C/C++ via an extension.

To start developing Git with VS Code, simply run the Unix shell script called init.sh in this directory, which creates the configuration files in .vscode/ that VS Code consumes. init.sh needs access to make and gcc, so run the script in a Git SDK shell if you are using Windows.