Fix Database Tracking Issue: Remove SQLite DB from Git History and Prevent Future Tracking

[Venkatkalyan21]

Problem

The SQLite database file wardha.db was previously tracked by Git, which introduced several issues:

Security Risk: Sensitive user data could be exposed if pushed to a public repo.

Repository Bloat: Database files increase repo size and slow down operations.

Merge Conflicts: Binary databases cause unresolvable conflicts between branches.

Bad Practice: Databases are runtime artifacts, not source code, so they shouldn't be version-controlled.

Solution

This PR includes the following fixes:

Updated .gitignore

Added *.db pattern to block database files from being tracked

Removed Database from Git History

Used history rewriting to remove wardha.db from all past commits (269 commits processed)

Updated README.md

Added a Database Setup section under Quick Start

Contributors now generate their own local database by running python app.py

Changes Made

.gitignore: Added ignore rule for SQLite databases

README.md: Added instructions for DB creation

Git history rewritten to fully remove tracked DB artifacts

Testing

Verified python app.py regenerates the database locally

Confirmed .gitignore prevents future staging of .db files

Acceptance Criteria

✅ Database file removed from repository
✅ .gitignore correctly ignores *.db
✅ Documentation updated for new contributors

[github-actions]

Thanks for creating a PR for your Issue! ☺️

We'll review it as soon as possible.
In the meantime, please double-check the file changes and ensure that all commits are accurate.

If there are any unresolved review comments, feel free to resolve them 🙌🏼.