Search a VS Code workspace with deliberate include and exclude rules

Start with a search, not a bulk edit

A workspace search is useful when you do not know which files contain the relevant text. Read the result paths and surrounding context before deciding to replace anything. Identical strings can play different roles across configuration, generated files, tests and source code, even when all matches look plausible in a compact result list.

Use the scope controls

Include and exclude patterns, ignore-file handling and other search settings affect the result set. Inspect those controls when a known file does not appear or when too many unrelated files match. A missing result is not proof that the text is absent from every place on disk outside the current workspace.

Review changes as a diff

Before applying a broad replacement, verify both the query and replacement text on a small subset. Afterward, inspect the resulting file changes and run checks appropriate to the project. Search convenience should not remove the review step that protects against unintended edits across multiple files.

Documented commands for this workflow

Scroll the table sideways to see every column.

Keep going

• Find and replace text inside the current VS Code file
• Rename a VS Code symbol instead of replacing similar text