fix: correct import path for ContributorIssueRecommendations from sibling to parent directory

[tmdeveloper007]

Summary

Fixes the broken import of ContributorIssueRecommendations in RepositoryInsights.tsx. The component file lives at src/components/ContributorIssueRecommendations.tsx but was imported from ./ContributorIssueRecommendations (sibling path) instead of ../ContributorIssueRecommendations (parent path).

Changes

• src/components/repository/RepositoryInsights.tsx: Fixed import path from ./ContributorIssueRecommendations to ../ContributorIssueRecommendations

Impact

Without this fix, the repository analysis page fails to build because the import resolves to a non-existent path.

Closes #2418

[vercel]

Someone 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 57 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: afebf128-297e-485f-a6e8-93d4ecc85131

📥 Commits

Reviewing files that changed from the base of the PR and between cd4e69b and eeb15f6.

📒 Files selected for processing (1)

• src/components/repository/RepositoryInsights.tsx

✨ 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]

⚠️ GSSoC Quality Check Failed — PR #2454

Hi @tmdeveloper007! 👋 Your PR has been flagged by our automated GSSoC quality check.

Issues found:

• 📏 Trivially small change — Only 2 line(s) changed in 1 file. Changes this small are almost never meaningful contributions. Make sure your PR solves a real issue.

---

✅ How to fix this

1. Read the issues listed above carefully
2. Edit your PR title and description to address them
3. Make sure your PR is linked to an open issue using closes #<issue-number>
4. Make sure your changes are meaningful and solve a real problem

Once you've fixed these, a maintainer will review and remove the flag. If you believe this is a mistake, please comment below. 🙏

GSSoC'26 automation · Maintainer: @nisshchayarathi

[tmdeveloper007]

CI status: Lint passing, CodeQL passing. Type Check failure is pre-existing on upstream/main (confirmed). Vercel preview failure is a maintainer-level authorization issue, not a code failure.