Excluded Files

ThinkReview focuses on reviewing the code that matters most. To keep reviews efficient and relevant, certain files are automatically excluded from the review process.

Why exclude files?

Code reviews should focus on the code you write, not on files that are:

• Generated automatically — Build outputs, compiled code, minified files
• Third-party dependencies — Vendor libraries, node_modules, package files
• Configuration artifacts — Lock files, generated configs
• Temporary files — Logs, cache files, temporary outputs

By excluding these files, ThinkReview:

• Saves time — Faster reviews by focusing on your code
• Reduces noise — More relevant feedback on what you actually wrote
• Lowers costs — Less content to analyze means more efficient reviews
• Improves accuracy — AI focuses on reviewable code, not generated artifacts

What gets excluded?

ThinkReview automatically excludes common patterns:

Build and Generated Files

• build/, dist/, out/, target/
• *.min.js, *.min.css
• Compiled binaries and executables
• Generated documentation

Dependencies

• node_modules/
• vendor/, lib/ (when containing third-party code)
• Package lock files (package-lock.json, yarn.lock, pnpm-lock.yaml)

Configuration Artifacts

• Generated config files
• IDE-specific files (.idea/, .vscode/)
• OS-specific files (.DS_Store, Thumbs.db)

Temporary and Cache Files

• Log files (*.log)
• Cache directories
• Temporary build artifacts

How it works

When you request a review, ThinkReview:

1. Scans the changed files in your merge request
2. Filters out excluded patterns automatically
3. Reviews only the relevant code you wrote
4. Provides focused feedback on your actual changes

You don’t need to configure anything—it just works.

---

TL;DR: ThinkReview automatically excludes generated files, build outputs, and dependencies to keep reviews focused on your code. This makes reviews faster, more relevant, and more cost-effective. Your source code and configuration files are always reviewed.