Where Does Greptile Store Review Configuration?
Greptile review rules and dashboard state, and the repo files that actually control reviews.
Last updated
Greptile reviews pull requests from the cloud. Rules, watched paths and reviewer routing live in your Greptile account and linked repo settings. There is no local database to back up.
The repo checkout below is where you would place any checked in config the team shares. History, comments and billing stay in the dashboard. When reviews vanish, check the GitHub App link first.
Where Greptile stores this, by platform
C:\Users\[Username]\Documents\GitHub\[Repo]\.greptile
Dashboard holds history and org rules. Keep any repo level config beside code so every clone inherits it. Local extension cache is disposable.
~/Documents/GitHub/[Repo]/.greptile
Same repo relative idea on every OS. Exact config filename follows current Greptile docs, so confirm in dashboard when the folder looks empty.
~/projects/[Repo]/.greptile
If no local config exists, the dashboard alone drives reviews. That is normal for newer installs. Do not invent files to fill the gap.
Frequently asked questions
Where do Greptile review rules live?
Keep review config in the repo (config file or dashboard linked rules) and commit it. Dashboard settings apply org wide. Repo files win for that project when both exist.
Where is Greptile review history?
Open the Greptile dashboard for the repo and check linked pull requests. Local folders hold no review history. Reconnect the GitHub App when reviews stop appearing.
Notice an outdated path? Let us know.