feat: `tsconfig.tsbuildinfo` is committed to the repository — this TypeScript build artifact belongs in .gitignore and creates unnecessary diff noise in PRs

[divyanshim27]

🐛 Problem Statement

tsconfig.tsbuildinfo is committed at the repository root. This file is a TypeScript incremental compilation cache — it records the file hashes and output structure of the last tsc build run. It is:

1. Machine-specific: generated from the local file system paths on the developer's machine
2. Auto-regenerated: recreated on every tsc invocation — committing it is pointless
3. Merge-conflict-prone: two PRs that both change TypeScript files will have conflicting tsconfig.tsbuildinfo changes, causing unnecessary merge conflicts
4. Confusing to contributors: new contributors see this file and wonder if they need to maintain it

The .gitignore file is present but *.tsbuildinfo is not listed.

Fix Required

# Remove from tracking
git rm --cached tsconfig.tsbuildinfo

# Add to .gitignore
echo "*.tsbuildinfo" >> .gitignore
echo "tsconfig.tsbuildinfo" >> .gitignore

git commit -m "chore: remove tsconfig.tsbuildinfo from version control"

Also check whether .vscode/ settings should be gitignored or if they serve a useful contributor purpose (editor recommendations are worth keeping, personal settings are not).

Files to Modify

File	Change
tsconfig.tsbuildinfo	Remove from git tracking
.gitignore	Add *.tsbuildinfo pattern

Suggested labels: chore, good first issue

I would like to work on this. Could you please assign it to me?

[github-actions]

Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.

Don't raise PR unless assigned to you.

In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Resources which can help you know more about Github 👇🏻

1. End to End GitHub Beginner Playlist: GitHub Playlist.

2. Build your GitHub Profile: GitHub Profile Optimisation.

3. GitHub Handbook for dummies: GitHub Blog for Beginners.

[github-actions]

Thanks for opening this issue. To help maintainers review it faster, please add the missing details below:

• Confirmation that tsconfig.tsbuildinfo is currently committed in the repository.
• A clear definition of expected behavior after the fix is applied.
• Any relevant details about how to determine whether .vscode/ settings should be gitignored.
• Information on the repository's current versioning or branching strategy (if applicable).

[divyanshim27]

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

[github-actions]

✅ This issue has been closed. Thank you for your contribution!