Problem Statement:
tsconfig.tsbuildinfo is present as a tracked file at the repo root. This file is TypeScript's incremental-build cache, auto-generated by tsc on every type-check/build, and is meant to be machine-local and regenerable — it should never be committed to version control.
Why this matters:
A committed .tsbuildinfo file can cause misleading incremental-build behavior for other contributors (stale cache referencing file states that no longer match their checkout), and needlessly changes on every local build, creating unnecessary diff noise in PRs if a contributor's editor/IDE regenerates it and it gets accidentally included in a commit.
Proposed Solution:
Add *.tsbuildinfo to .gitignore (currently a .gitignore exists at root but evidently doesn't cover this pattern).
Run git rm --cached tsconfig.tsbuildinfo to untrack it going forward.
Quick repo-wide check for any other stray build artifacts (e.g., .docusaurus/ cache folder) that might have been accidentally committed the same way.
Impact: Small but genuine hygiene fix that prevents confusing incremental-build diffs for the project's large and active contributor base (142 forks).
Problem Statement:
tsconfig.tsbuildinfo is present as a tracked file at the repo root. This file is TypeScript's incremental-build cache, auto-generated by tsc on every type-check/build, and is meant to be machine-local and regenerable — it should never be committed to version control.
Why this matters:
A committed .tsbuildinfo file can cause misleading incremental-build behavior for other contributors (stale cache referencing file states that no longer match their checkout), and needlessly changes on every local build, creating unnecessary diff noise in PRs if a contributor's editor/IDE regenerates it and it gets accidentally included in a commit.
Proposed Solution:
Add *.tsbuildinfo to .gitignore (currently a .gitignore exists at root but evidently doesn't cover this pattern).
Run git rm --cached tsconfig.tsbuildinfo to untrack it going forward.
Quick repo-wide check for any other stray build artifacts (e.g., .docusaurus/ cache folder) that might have been accidentally committed the same way.
Impact: Small but genuine hygiene fix that prevents confusing incremental-build diffs for the project's large and active contributor base (142 forks).