Do I need to commit .gitignore?

Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.

How do I add custom patterns?

Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.

How do I ignore a file that is already tracked?

Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached to stop tracking it without deleting the file locally.

Should I commit .vscode/settings.json?

It depends. Project-wide settings (formatter, tab size) benefit everyone and should be committed. Personal preferences should go in User Settings instead.

.gitignore for Visual Studio Code

VS Code editor settings, workspace configuration, and extension cache files.

Quick presets

Selected (1)

Visual Studio Code

Your selections never leave your browser. Generation happens entirely client-side.

Raw

8 patterns · 320 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: Visual Studio Code
# 2026-04-20

# ---- Visual Studio Code ----
# Visual Studio Code
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
!.vscode/*.code-snippets
.history/
*.vsix

What this template ignores

Ignores VS Code workspace state and cache while keeping shared team settings like settings.json, tasks.json, launch.json, and extensions.json committed.

Common additions

+.vscode/settings.json — if you prefer not to share workspace settings

Commonly paired with

macos windows node Combine →

Frequently asked questions

Do I need to commit .gitignore?: Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
How do I add custom patterns?: Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
How do I ignore a file that is already tracked?: Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
Should I commit .vscode/settings.json?: It depends. Project-wide settings (formatter, tab size) benefit everyone and should be committed. Personal preferences should go in User Settings instead.

Looking for something else? Browse all templates →