You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
🐞[Bug]: Wrong href and non-semantic card links in Community section #2519
In src/components/Community/index.tsx, the card for "Community Forks" in generateList specifies:
{stat: githubForksCount,statText: githubForksCountText,description:
"Forks of our repositories the community extends and builds on our work.",href: "https://github.com/orgs/recodehive/discussions",label: "Community Forks",}
When users click on the "Community Forks" card, they are incorrectly taken to GitHub Discussions (https://github.com/orgs/recodehive/discussions) instead of the organization's repositories page (https://github.com/orgs/recodehive/repositories).
Furthermore, the stat items are rendered using <div> elements with onClick={() => handleCardClick(item.href)} and window.open rather than standard semantic <a> anchor tags. This prevents standard browser functionality such as right-click ("Open in new tab"), middle-click to open in background, copying link addresses, and standard keyboard/screen reader link navigation. In addition, unused useEffect and useState imports remain in the file.
Expected behavior
The "Community Forks" card should point to https://github.com/orgs/recodehive/repositories.
The stat cards should be rendered as semantic <a> anchor tags with target="_blank" and rel="noopener noreferrer" so standard link navigation, right-click, and assistive technologies work properly.
Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.
Don't raise PR unless assigned to you.
In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊
Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.
We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰
🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨
📚Resources which can help you know more about Github 👇🏻
Activity
github-actions commentedon Nov 14, 2026
Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.
Don't raise PR unless assigned to you.
In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊
Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.
We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰
🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨
📚Resources which can help you know more about Github 👇🏻
End to End GitHub Beginner Playlist: GitHub Playlist.
Build your GitHub Profile: GitHub Profile Optimisation.
GitHub Handbook for dummies: GitHub Blog for Beginners.
github-actions commentedon Nov 14, 2026
Thanks for opening this issue. To help maintainers review it faster, please add the missing details below:
bobby404-K commentedon Nov 14, 2026
assign me @sanjay-kv
sanjay-kv commentedon Nov 15, 2026
this is how it meant to be, wanted to redirect to discussion @bobby404-K
github-actions commentedon Nov 15, 2026
✅ This issue has been closed. Thank you for your contribution!
bobby404-K commentedon Nov 15, 2026
makes sense, yeah it should redirect.