chore: untrack tsconfig.tsbuildinfo across the monorepo

[hallelx2]

Self-inflicted, from #17 — a git add apps/blogs swept in apps/blogs/tsconfig.tsbuildinfo.

It is TypeScript incremental build state: machine-local, rewritten on every compile, and a source of pointless diffs and merge conflicts for anyone else building the app.

apps/web had the same file already tracked, from before this work. Leaving it while adding *.tsbuildinfo to .gitignore would be incoherent, so both go.

.gitignore covered node_modules/ and .next/ but not this, which is why nothing stopped it landing — so the pattern is added as well as the files removed.

Untracked with update-index --force-remove, so the files stay on disk and nobody loses their incremental cache. Verified both are still present locally after staging.

Summary by Sourcery

Chores:

• Remove tracked tsconfig.tsbuildinfo files from apps/blogs and apps/web and add a gitignore rule to exclude *.tsbuildinfo going forward.

[sourcery-ai]

Sorry @hallelx2, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vectorless-web	Building	Preview	Aug 4, 2026 9:01pm

[coderabbitai]

Warning

Review limit reached

@hallelx2, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 48 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6054c2e3-1625-45d1-a86b-e0a58617ba9d

📥 Commits

Reviewing files that changed from the base of the PR and between 34f2b90 and 045a4c5.

📒 Files selected for processing (3)

• .gitignore
• apps/blogs/tsconfig.tsbuildinfo
• apps/web/tsconfig.tsbuildinfo

---

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.}

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Stop tracking TypeScript incremental build artifacts (tsconfig.tsbuildinfo) in the monorepo and ensure future builds don’t reintroduce them into version control.

File-Level Changes

Change	Details	Files
Stop committing TypeScript incremental build state files and rely on local, untracked caches instead.	Removed the tracked tsconfig.tsbuildinfo artifact from the blogs app. Removed the tracked tsconfig.tsbuildinfo artifact from the web app. Configured gitignore to exclude all *.tsbuildinfo files across the repo.	apps/blogs/tsconfig.tsbuildinfo apps/web/tsconfig.tsbuildinfo .gitignore

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[hallelx2]

Correction to the PR body: I wrote that untracking would leave the files on disk so nobody loses their incremental cache. That is true at the moment of staging, but not on pull — when this commit lands, git removes the files from the working tree because they go from tracked to untracked. I saw it happen locally on
eset --hard.

The consequence is trivial — one slower typecheck while the cache rebuilds — but the claim as written was wrong, so recording it rather than leaving it in the history.

Verified after the merge: the app builds clean with the cache absent, all 7 posts still prerender, and \git status\ stays clean, so the ignore pattern is doing its job.