Configuration Methods
- .greptile/ folder (Recommended)
- greptile.json
- Dashboard UI
A folder you place in any directory of your repo. Supports cascading — root-level defaults with per-directory overrides.
- Version controlled and reviewed in PRs
- Separate files for settings, rules, and context
- Per-directory overrides for monorepos
- Structured rules with scoping, severity, and disable-by-ID
How They Interact
When multiple methods are used, settings are resolved in this order (highest priority first):- Org enforced rules — set by admins in the dashboard, cannot be overridden
.greptile/folder — per-directory and repo-wide settingsgreptile.json— repo-wide settings (ignored if.greptile/exists in the same directory)- Org default rules — dashboard defaults, overridden by any repo-level config
If both
.greptile/ and greptile.json exist in the repository root, .greptile/ takes precedence and greptile.json is ignored.In This Section
.greptile/ Configuration
How cascading works, merge rules, monorepo examples
.greptile/ File Reference
Complete schema for config.json, rules.md, and files.json
Controlling Nitpickiness
Adjust strictness, filter comment types, ignore files
Training the Learning System
Use reactions and feedback to improve reviews
Custom Standards
Enforce team-specific coding rules
Pattern Repositories
Reference related codebases
greptile.json Reference
Legacy format — complete parameter documentation