chore: delete the two SQLite databases committed into the tree - #366
Open
ywatanabe1989 wants to merge 1 commit into
Open
chore: delete the two SQLite databases committed into the tree#366ywatanabe1989 wants to merge 1 commit into
ywatanabe1989 wants to merge 1 commit into
Conversation
Two real SQLite database files were tracked in this repository: .scitex/clew/runtime/db.sqlite 69,632 bytes examples/_legacy/scitex/clew/multi_parent/scitex/clew.db 94,208 bytes Neither is referenced by any code. Both are stale artefacts of a clew runtime that no longer exists, and the repository already says so in two places without ever having removed them: .gitignore:930 **/scitex/clew.db .scitex/dev/config.yaml "stale orphan dir (clew.db inside; ...)" An ignore rule does not untrack a file that is already tracked, which is why `clew.db` survived being explicitly ignored. That is the whole story of how a 94 KB database sat in a Python package's examples directory. WHY THE OTHER ONE GOT IN: .gitignore listed `db.sqlite3` and `db.sqlite3-journal` but NOT `db.sqlite`, so `.scitex/clew/runtime/db.sqlite` matched nothing. Added `db.sqlite` beside `db.sqlite3` in both ignore blocks so the same gap cannot be walked through again. After this, `git ls-files` matching `\.db$|\.sqlite$|\.sqlite3$` returns nothing in this repository. Part of the fleet-wide SQLite eradication. Deliberately NOT touched: scitex-db, crossref-local and openalex-local, which are named exceptions and whose databases must survive.
ywatanabe1989
enabled auto-merge (squash)
August 30, 2026 10:24
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two real SQLite database files were tracked in this repository:
.scitex/clew/runtime/db.sqliteexamples/_legacy/scitex/clew/multi_parent/scitex/clew.dbNeither is referenced by any code. Both are stale artefacts of a clew runtime that no longer exists — and the repository already says so, in two places, without ever having removed them:
An ignore rule does not untrack a file that is already tracked. That is the whole story of how a 94 KB database sat in a Python package's examples directory while being explicitly ignored.
How the other one got in
.gitignorelisteddb.sqlite3anddb.sqlite3-journalbut notdb.sqlite, so.scitex/clew/runtime/db.sqlitematched nothing at all. This PR addsdb.sqlitebesidedb.sqlite3in both ignore blocks (lines 147 and 393) so the same one-character gap cannot be walked through again.Verification
After this change,
git ls-filesfiltered on\.db$|\.sqlite$|\.sqlite3$returns nothing in this repository.Scope
Part of the fleet-wide SQLite eradication. Deliberately not touched:
scitex-db,crossref-localandopenalex-local— named exceptions whose databases must survive.