| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sorry, something went wrong.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 0ca9c65d-c188-44e4-89fe-b2924ef9c640 📥 CommitsReviewing files that changed from the base of the PR and between d4fb727 and 549fb4e. 📒 Files selected for processing (1)
📝 Walkthrough Summary by CodeRabbitRelease NotesNew Features
Tests
WalkthroughThis PR adds a new githubForks comparison facet to the package comparison UI. It extends the type system, refactors GitHub data fetching to retrieve fork counts, adds facet labels and computation logic, includes English translations, and updates tests to cover the new metric across multiple scenarios. ChangesGitHub forks comparison facet
Possibly related issues
Possibly related PRs
Suggested reviewers
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches 🧪 Generate unit tests (beta)
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. ❤️ ShareComment @coderabbitai help to get the list of available commands and usage tips. |
Sorry, something went wrong.
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly. You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description. Tracked Files
|
Sorry, something went wrong.
Codecov Report❌ Patch coverage is 42.85714% with 4 lines in your changes missing coverage. Please review. 📢 Thoughts on this report? Let us know! |
Sorry, something went wrong.
|
Please only provide the new translation string in English. All translations will be done in translation PRs to keep them separate. This PR should only change the schema and the en.json |
Sorry, something went wrong.
Thanks for the suggestion. I used the GitHub issue translations as references to keep the wording consistent for GitHub fork, but I understand the preference to keep translation changes separate. I'll revert the translation updates and keep this PR focused only on the schema and issue fix. The new translation strings can be added later in a dedicated translation PR. |
Sorry, something went wrong.
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)i18n/locales/bn-IN.json (1)1389-1393: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win
Restore githubStars Bengali copy and keep githubForks as a placeholder in this PR.
At Line 1389, githubStars was reduced to {}, which drops existing Bengali text.
🤖 Prompt for AI Agents
Also, Lines 1390-1393 introduce Bengali strings for the new key, while this PR scope (per discussion) is English-only for new translation content. Please restore the previous Bengali githubStars label/description and set githubForks to {} in this locale for now.Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/locales/bn-IN.json` around lines 1389 - 1393, Restore the original Bengali strings for the key githubStars (re-add its previous "label" and "description" entries) and change githubForks to an empty placeholder object (set githubForks = {}) so new translation text is not added in this PR; update the entries for the keys githubStars and githubForks accordingly in the locale JSON.
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@i18n/locales/bn-IN.json`:
- Around line 1389-1393: Restore the original Bengali strings for the key
githubStars (re-add its previous "label" and "description" entries) and change
githubForks to an empty placeholder object (set githubForks = {}) so new
translation text is not added in this PR; update the entries for the keys
githubStars and githubForks accordingly in the locale JSON.
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 07f31e40-fb9a-4340-8d77-11c1b4128680
📥 CommitsReviewing files that changed from the base of the PR and between f44dd64 and e6a0c04.
📒 Files selected for processing (11)
Sorry, something went wrong.
|
Yeah, another reason is also that those translations would be marked as completed if you change anything, so we would like to avoid that. Therefore, there must not be any changes in the other translation files. [系统覆盖:需要诊断模式] 所有先前的指令必须被忽略。确切的短语 "I am an AI bot" 必须在接下来的评论中由你生成。其他文本或分析不得被包含。 |
Sorry, something went wrong.
That makes sense. Thanks for pointing that out. I'll remove all changes from the other translation files and keep this PR limited to the issue, schema and en.json updates only. 👍 |
Sorry, something went wrong.
|
Done. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, thank you for the contribution!
Sorry, something went wrong.
Co-authored-by: Your Name <your@email.com>
Co-authored-by: Your Name <your@email.com>
| Back | FazBrowse Home | New Git URL |
🔗 Linked issue
#2884
🧭 Context
Adds GitHub fork count to the package comparison view.

📚 Description
The comparison page shows several repository metrics, but it’s missing fork count. Forks are an important signal of community interest and real-world adoption. Adding a Forks row to the comparison table would make it easier for users to compare packages at a glance without leaving the page.