Repository navigation
chore: collapse drizzle snapshots in diffs and CodeRabbit reviews - #81
Conversation
drizzle-kit writes a full copy of the schema with every migration. Mark the snapshots as generated so GitHub collapses them and local diffs show one line, and keep CodeRabbit on the .sql migrations. The CodeRabbit file inherits the UI settings, so nothing else changes.
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Snapshot review and diff settings .coderabbit.yaml, .gitattributes |
CodeRabbit review filters exclude Drizzle snapshot JSON files. Git attributes mark them as generated and exclude them from local diff output, while merges continue to treat them as text. |
Priority:
Change: Other
Merge Risk: 
Minimal · up to 0cde5
-
The change suppresses snapshot diffs while preserving text merges and excludes only the intended generated snapshots from review.
Pre-merge checks: 
4
-
Full details: Title check
-
Explanation
The title "chore: collapse drizzle snapshots in diffs and CodeRabbit reviews" matches the main change. The PR marks drizzle/meta/*_snapshot.json as generated in .gitattributes so GitHub and local git diff collapse them, and it adds a CodeRabbit path_filters exclusion for the same files in .coderabbit.yaml. The title is specific, concise, and free of file lists or vague terms.
Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Every migration comes with
drizzle/meta/NNNN_snapshot.json, a full copy of the schema (~2,500 lines) that drizzle-kit diffs against to write the next migration. Nothing reads them at runtime. They drown out the.sqlmigration in reviews..gitattributes:drizzle/meta/*_snapshot.json linguist-generated=true -diffgit diffprints one line per snapshot;git diff --textstill shows the content._journal.jsonand the.sqlmigrations are untouched..coderabbit.yaml:path_filters: ["!drizzle/meta/*_snapshot.json"], so CodeRabbit reviews the migrations, not the snapshots.inheritance: truekeeps every setting made in the CodeRabbit UI; without it, a repo file replaces them.Same change as PoliNetworkOrg/backend#108.