fix: Stop tracking ChromaDB SQLite files to prevent merge conflicts

[sharma-sugurthi]

Closes #173

Problem

Backend/db/chromadb/chroma.sqlite3 was tracked in version control, causing merge conflicts after every backend run since ChromaDB modifies the binary file at runtime.

Solution

• ✅ Added ChromaDB SQLite files to Backend/.gitignore
• ✅ Removed chroma.sqlite3 from Git tracking (preserved locally)
• ✅ Database auto-recreates on backend startup via chromadb.PersistentClient

Verification

• Analyzed agent/vector_store.py - database initializes automatically
• Confirmed 0 embeddings in current DB (no seed data loss)
• Collections auto-create via get_or_create_collection()
• Tested locally: file persists after git rm --cached

Impact

• ✅ Eliminates merge conflicts for all contributors
• ✅ No functionality change (backend behavior identical)
• ✅ Cleaner git status for developers

Summary by CodeRabbit

• Chores
  • Updated repository configuration to better manage database files in version control.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates Backend/.gitignore to exclude ChromaDB SQLite database files and related temporary files by adding three ignore patterns: *.sqlite3, *.sqlite3-shm, and *.sqlite3-wal. This prevents version control from tracking runtime-modified database artifacts.

Changes

Cohort / File(s)	Change Summary
Gitignore Configuration Backend/.gitignore	Added three patterns to exclude ChromaDB SQLite database files (*.sqlite3, *.sqlite3-shm, *.sqlite3-wal) from version control

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 Hop, skip, and away with these databases of change,
No more merge conflicts in version control's range!
SQLite files dance freely, untracked and untamed,
ChromaDB flourishes bright, unshamed and unclaimed. 🌿✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR implements most core requirements from #173: added ignore patterns for SQLite files and removed tracked binaries. However, README documentation and database seeding/removal verification are not addressed in this changeset.	Add a README note documenting auto-initialization behavior and clarify whether the database contained seed data or should be removed from the repo.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: stopping tracking of ChromaDB SQLite files to prevent merge conflicts.
Out of Scope Changes check	✅ Passed	Only Backend/.gitignore was modified, which is directly related to the linked issue requirements. No extraneous or unrelated changes detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}