[FIX]: #968 Duplicate Arrows Appearing After Link Text in GitHub Badges

[kanishka-commits]

Description

Fixes #968

This PR fixes the issue where duplicate arrows appear after the link text in the GitHub achievement badges section. One arrow was coming from the CSS styling and another was hardcoded in the HTML. The PR removes the hardcoded arrow to ensure only a single arrow appears, improving visual consistency and readability.

Screen.Recording.2025-10-20.at.1.49.39.PM.mov

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify):

Changes Made

• Removed the hardcoded arrow (→) from the innerHTML of GitHub badge links.
• Verified that CSS styling provides the single arrow consistently.
• Tested the layout in both light and dark modes to ensure uniform appearance.
• Ensured no duplicate arrows appear after link text.

Dependencies

• No new dependencies introduced.
• No version updates required.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices.
• My changes do not generate new console warnings or errors.
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

[vercel]

@kanishka-commits is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps 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 PR 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 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[github-actions]

Synced data from Linked Issues

Labels:

• level 1
• recode
• hacktoberfest-accepted

Assignees:

• kanishka-commits

Milestones:

• recode:launch 3.0

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
recode-website	Ready	Preview	Comment	Oct 21, 2025 2:41pm

[kanishka-commits]

@sanjay-kv @iitzIrFan
Hey! When I opened this issue, it was under GSSoC. Could you please add the GSSoC label to it?
Thanks!

[kanishka-commits]

Thankyou @iitzIrFan
Also the level label is missing, can you kindly add it?

[iitzIrFan]

It will work as the issue is linked with this pr