chore: keep the live henza data dump out of git
oapi.sql is the owner's full data dump of the legacy database: customers' names, mobiles and addresses. It was untracked but not ignored, so a single `git add .` would have committed it and a push would have sent it to the remote. Only the structure-only oapi-struncture.sql belongs in the repo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
4d3b15c3b9
commit
5bacade748
@@ -15,3 +15,7 @@ apps/api/storage/uploads/*
|
||||
# apps/api/release/app.js + apps/api/release/vendor/ (Prisma)
|
||||
# apps/admin-panel/dist/
|
||||
# apps/user-app/dist/
|
||||
|
||||
# Live henza data dump (customers' personal data). Never commit.
|
||||
# Only the structure-only oapi-struncture.sql belongs in the repo.
|
||||
/oapi.sql
|
||||
|
||||
Reference in New Issue
Block a user