grepai-ignore-patterns

To exclude test files and build outputs from code search indexing, configure ignore patterns in your .grepai/config.yaml file under the ignore key to filter out non-source artifacts from your search results.

Yes, you can use existing .gitignore rules to exclude vendored code from indexing. The system honors existing .gitignore entries to align indexing exclusions with your repository-level configurations automatically.

The best way to reduce noise in codebase search results is to apply user-defined ignore patterns via configuration, excluding generated code, caches, and vendor dependencies from the indexing process to improve search quality.

To configure ignore patterns in .grepai/config.yaml for project indexing, add your target exclusion patterns under the ignore key, then run grepai watch to re-index the codebase with the newly defined rules applied.

Yes, GrepAI ignore patterns configuration works with codebases of any programming language. It universally applies user-defined exclusion rules to filter out tests, vendored code, and build outputs regardless of the project's language stack.

No, you do not need external tools to set up ignore patterns for code indexing. The configuration relies solely on standard settings within .grepai/config.yaml and existing .gitignore rules without requiring any additional dependencies.