## 🧹 [Housekeeping] `.turbo/` Turborepo cache artifacts and `issues.md` planning document are committed to the repository

[prince-pokharna]

Summary

Two categories of files that should not be version-controlled are committed:

1. .turbo/ directory:
Turborepo's local task cache (.turbo/) contains hashed build outputs specific to the local machine's file paths, timestamps, and environment. Committing it:

• Creates merge conflicts between contributors on different machines
• Inflates repository size with binary cache data
• Causes confusing Turborepo cache misses when the cache doesn't match the current machine's state
• Is explicitly documented in Turborepo's own .gitignore templates as something to exclude

2. issues.md at the repository root:
This file appears to be an internal planning document — similar to TODO.md in other projects. As a committed file, it:

• Cannot be assigned to contributors for GSSOC point tracking
• Cannot be linked to PRs for automatic closure
• Will become stale and misleading as issues are resolved
• Is not discoverable through GitHub's issue tracker for contributors looking for tasks to work on

Proposed Fix

Remove .turbo/ from tracking:

git rm -r --cached .turbo/

Update .gitignore:
Turborepo
.turbo/

Migrate issues.md content:

• Create GitHub Issues for each item listed in issues.md with appropriate labels (bug, enhancement, good first issue)
• Delete issues.md from the repository
• Add a GitHub Project board linked from the README for roadmap tracking

Acceptance Criteria

• .turbo/ removed from git tracking and added to .gitignore
• issues.md items migrated to actual GitHub Issues with labels
• issues.md removed from the repository
• turbo run dev works correctly after the .turbo/ removal

Labels: housekeeping, documentation, good first issue

[prince-pokharna]

Hey @AnirbansarkarS ,
Please assign it to me under GSSoC 2026.
/assign /claim /claim-assignment