feat : store analyzedCommitSha and detect stale analysis on repository fetch

[tmdeveloper007]

Summary

After a successful repository analysis, store the default-branch HEAD commit SHA. When the repository is fetched, compare against the latest local commit SHA and surface a isStale flag so the frontend can show an "Analysis may be outdated" warning with a re-run option.

Changes

• prisma/schema.prisma: Add analyzedCommitSha optional String field to Repository model
• lib/services/repositoryService.ts:
  • analyzeRepository: Record analyzedCommitSha after successful analysis completion
  • getRepository: Query latest local commit SHA and compare with analyzedCommitSha; return { ...repo, isStale }

Impact

Users see a clear indicator when their repository analysis is based on an outdated commit, prompting them to re-run analysis for accurate results.

Closes #2392

[vercel]

@tmdeveloper007 is attempting to deploy a commit to the Nisshchaya's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@tmdeveloper007, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 59 minutes and 57 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ec386870-d915-40c9-a756-c352e0a10e94

📥 Commits

Reviewing files that changed from the base of the PR and between d4e21a5 and 953deee.

📒 Files selected for processing (2)

• lib/services/repositoryService.ts
• prisma/schema.prisma

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[github-actions]

🎉 Thanks for your contribution, @tmdeveloper007!

Your PR has passed our automated GSSoC quality checks. Here's a quick summary:

Check	Status
PR description	✅ Provided
PR title	✅ Meaningful
Linked issue	✅ Found
Change size	✅ Looks good (102 lines across 2 file(s))

A maintainer will review your PR soon. Please be patient and available for feedback. 💪

GSSoC'26 automation · Maintainer: @nisshchayarathi

[tmdeveloper007]

CI Status

CI checks ran. The Type Check and verify failures are pre-existing on main (confirmed: Type Check has been failing on main since 2026-06-19; verify failures predate this PR).

PR-specific changes:

• PR fix : handle P2002 unique constraint when re-adding deleted repository #2445: Only modifies lib/services/repositoryService.ts — CI: all checks pass.
• PRs fix : propagate HttpError with 429 status for Gemini quota errors to callers #2446-chore : update copyright year in LICENSE from 2025 to 2026 #2449: Pre-existing Type Check / verify failures; no new failures introduced by these changes.

All changes are isolated to the files described in the PR body. The pre-existing CI failures require a separate investigation and are outside the scope of these fixes.

[tmdeveloper007]

Closing this PR. The branch is based on an older commit of upstream/main and has drifted from the current main. The upstream repository has received significant updates since this PR was opened, causing CI type-check and test failures due to merge conflicts with the base branch. Please re-open as a fresh PR against the current main if the fix is still needed.