IgnoreKit

Keep generated files, local settings, build output, and other unwanted files out of source control without editing ignore files by hand.

IgnoreKit adds a simple action to the VS Code Explorer. There is no setup: right-click a file or folder, choose where to ignore it, and continue working.

Installation

Find IgnoreKit in the VS Code Extensions view and select Install. No settings or project changes are required.

Getting Started

1. In the Explorer, right-click the file or folder you want to ignore.
2. Choose IgnoreKit: Add to Ignore File....
3. If IgnoreKit offers several choices, select the tool you want to ignore the item for.

To undo an IgnoreKit entry, right-click the same item and choose IgnoreKit: Remove from Ignore File....

Important: Git ignore rules only hide untracked files. If a file was already committed or staged, Git will continue to show it until it is untracked.

Why Use IgnoreKit?

• Updates the correct ignore file directly from the Explorer.
• Works with nested repositories, multi-root workspaces, and directory-level .gitignore files.
• Supports 16 common ignore-file formats for Git, npm, Docker, Prettier, ESLint, Helm, Terraform, Vercel, and more.
• Creates supported ignore files when they are missing.
• Protects your existing rules and any unsaved edits in an open ignore file.
• Prevents duplicate entries and keeps the Git Changes view in sync after updates.
• Uses portable paths that work across Windows, macOS, and Linux.

What Happens When You Add an Item?

IgnoreKit looks for the closest ignore file that applies to your selection. If there is one clear choice, it is updated immediately. If several tools apply, you will see a short list such as:

• .gitignore
• .npmignore (npm package)
• .dockerignore (Docker)

The path shown under each choice tells you which project or package will be updated. For Git, IgnoreKit uses the closest .gitignore or nested repository, so rules do not accidentally go into an unrelated project.

Supported Ignore Files

IgnoreKit only offers files that make sense for the selected project. Files marked “No” must already exist before they appear as a choice.

Your Existing Rules Stay Safe

IgnoreKit preserves the rest of your ignore file and writes to its own managed section:

# IgnoreKit
# Added from VS Code Explorer
dist/
# End IgnoreKit

The remove command only removes entries from this section. Rules you wrote elsewhere are left unchanged. If the ignore file is open with unsaved changes, IgnoreKit includes those changes instead of replacing them with an older copy from disk.

Clear Choices for Packages

For .npmignore and .vscodeignore, IgnoreKit shows the package manager it recognizes:

• Bun: bun.lock or bun.lockb
• pnpm: pnpm-lock.yaml
• Yarn: yarn.lock
• npm: package-lock.json

Other choices show the related tool name, such as .dockerignore (Docker).

Examples

Adding dist/ in a package that already has .npmignore may offer both:

• .gitignore
• .npmignore (npm package)

Adding .env at the workspace root writes:

/.env

Adding a folder writes:

dist/

Frequently Asked Questions

Why does an ignored item still appear in Git Changes?

• Check whether the file was already committed or staged. Ignore rules only hide untracked files.
• Make sure you chose .gitignore, rather than an ignore file for another tool.
• In a nested repository, run the command again and confirm the displayed path points to that repository.
• Refresh the Source Control view if another Git operation was running at the same time.

Does IgnoreKit delete or move my files?

No. It only adds or removes text rules in supported ignore files.

Can Remove from Ignore File delete my own rules?

No. It only removes rules previously placed inside the IgnoreKit section.

Does IgnoreKit work in monorepos and nested repositories?

Yes. It looks for the closest applicable ignore file and shows the target path when you need to choose.

Privacy

IgnoreKit runs entirely inside VS Code. It does not upload file paths, project data, or ignore-file contents.

Contributing

Issues and pull requests are welcome. Please keep changes focused, add tests for behavior changes, and run the validation commands before opening a pull request.

License

MIT. See the LICENSE file in this repository.