H.5 — Scrub dev.db from git history
What's wrong
dev.db (a SQLite file) was committed once and removed in commit c28731a. It's gitignored now via *.db, but the old version is still in git history — anyone who clones can git log -- dev.db and check it out.
Why it matters
The committed DB had test seeds, not real user data, so the actual data risk is low. But it's bad hygiene and clutters every clone.
How to fix
Use git filter-repo (the modern replacement for git filter-branch):
# Make a fresh clone first as a backup.
git clone --mirror git@github.com:UTDallasEPICS/Reading-MLK.git Reading-MLK.bak.git
# Then in your working clone:
pip install git-filter-repo
git filter-repo --path dev.db --invert-paths --force
git push --force origin main
Coordinate with the whole team before doing this: anyone with an existing clone needs to either re-clone, or reset their main to the new history.
Files
Severity
L (cosmetic).
Acceptance
H.5 — Scrub
dev.dbfrom git historyWhat's wrong
dev.db(a SQLite file) was committed once and removed in commitc28731a. It's gitignored now via*.db, but the old version is still in git history — anyone who clones cangit log -- dev.dband check it out.Why it matters
The committed DB had test seeds, not real user data, so the actual data risk is low. But it's bad hygiene and clutters every clone.
How to fix
Use
git filter-repo(the modern replacement forgit filter-branch):Coordinate with the whole team before doing this: anyone with an existing clone needs to either re-clone, or reset their
mainto the new history.Files
Severity
L (cosmetic).
Acceptance
git log -- dev.dbshows no commits.