Skip to content

Conversation

@PAGARE-MANGESH
Copy link

@PAGARE-MANGESH PAGARE-MANGESH commented Jan 19, 2026

Hello @Zahnentferner , @varunchitre15 , @heychirag #429

I've updated the Discord invitation link throughout the website to the new, valid one (https://discord.gg/xnmAPS7zqB).

Here are the files I updated:

src/components/Footer.jsx
src/pages/index.jsx
src/pages/apply.jsx
README.md
You can now test the link to ensure it correctly directs users to the AOSSIE Discord server.

image image

Summary by CodeRabbit

  • New Features

    • Project card links are now fully clickable, opening in a new tab.
  • Documentation

    • Updated Discord channel link across the site.
  • Chores

    • Updated icon library dependencies to latest versions.
    • Twitter icon updated to X icon throughout the interface.

✏️ Tip: You can customize this high-level summary in your review settings.

mangesh and others added 3 commits January 6, 2026 22:11
src/pages/projects.jsx
 to make the link display inline with the icon and text aligned correctly.
Signed-off-by: Mangesh Pagare <mangeshpagare8668@gmail.com>
@vercel
Copy link

vercel bot commented Jan 19, 2026

@PAGARE-MANGESH is attempting to deploy a commit to the AOSSIE Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai
Copy link

coderabbitai bot commented Jan 19, 2026

📝 Walkthrough

Walkthrough

The changes update social links and branding across the codebase: Discord invite URLs are migrated to a new server, Twitter icon imports are swapped to X branding, FontAwesome dependencies are upgraded to newer versions, and project card links are refactored for improved accessibility by wrapping them in anchor elements with updated hover styling.

Changes

Cohort / File(s) Summary
Discord Invite Link Migration
README.md, src/components/Footer.jsx, src/pages/apply.jsx, src/pages/index.jsx
Updated Discord invite URLs from hjUhu33uAn to xnmAPS7zqB across documentation and component social links
Twitter→X Branding & FontAwesome Upgrade
package.json, src/components/Footer.jsx, src/pages/index.jsx
Upgraded @fortawesome/free-brands-svg-icons (^6.2.1 → ^7.1.0) and @fortawesome/react-fontawesome (^0.2.0 → ^3.1.1); replaced faTwitter icon imports with faXTwitter to reflect X rebranding
Project Link Accessibility Enhancements
src/pages/projects.jsx
Wrapped project links in anchor tags with target="_blank" and rel="noopener noreferrer"; updated hover colors from #00843D to #32a852 for improved click-ability and UX

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A Discord rendezvous, a Twitter takes flight,
With X marks the icon, now shining so bright,
New links wrapped in anchors, so clickable-keen,
The freshest rebranding we've ever seen! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Fix discord link' accurately describes the primary change - updating the Discord invitation link across multiple files from an expired URL to a new valid one.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@PAGARE-MANGESH
Copy link
Author

Hi maintainers 👋
The Vercel check is failing because this PR is from a fork and does not have deployment permissions.
Please let me know if any changes are needed from my side.
Thanks!

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@package.json`:
- Around line 17-21: The package `@fortawesome/fontawesome-svg-core` is pinned to
6.2.1 but `@fortawesome/free-brands-svg-icons` is 7.1.0; update
`@fortawesome/fontawesome-svg-core` to a v7 range (e.g., ^7.0.0 or ^7.1.0) and
align the other FontAwesome packages (e.g., `@fortawesome/free-regular-svg-icons`,
`@fortawesome/free-solid-svg-icons`, `@fortawesome/react-fontawesome`) to compatible
v7 releases so all fontawesome packages use the same major version; after
updating the package.json entry names (e.g.,
"@fortawesome/fontawesome-svg-core": "^7.x"), run your package manager install
to refresh lockfiles and test for runtime/import issues.
🧹 Nitpick comments (2)
src/components/Footer.jsx (1)

48-49: Consider updating the aria-label to match the X branding.

The icon is now faXTwitter (X branding), but the aria-label still says "Follow on Twitter". For consistency and clarity for screen reader users, consider updating it to "Follow on X" or "Follow on X (Twitter)".

💡 Suggested fix
-                <Link aria-label="Follow on Twitter" className=' text-zinc-400 hover:text-[`#00843D`] dark:text-zinc-400 dark:hover:text-yellow-400 transition' href='https://twitter.com/aossie_org'>
+                <Link aria-label="Follow on X" className=' text-zinc-400 hover:text-[`#00843D`] dark:text-zinc-400 dark:hover:text-yellow-400 transition' href='https://twitter.com/aossie_org'>
src/pages/index.jsx (1)

91-96: Consider updating the aria-label to match the X branding.

Same as in Footer.jsx - the aria-label on line 92 says "Follow on Twitter" while the icon is now faXTwitter. Consider updating for consistency.

💡 Suggested fix
                  <Link
-                   aria-label="Follow on Twitter"
+                   aria-label="Follow on X"
                    className="text-zinc-500 transition hover:text-[`#00843D`] dark:text-zinc-400 dark:hover:text-yellow-400"
                    href="https://twitter.com/aossie_org"
                  >
                    <FontAwesomeIcon icon={faXTwitter} size="2xl" />
                  </Link>

Comment on lines 17 to +21
"@fortawesome/fontawesome-svg-core": "^6.2.1",
"@fortawesome/free-brands-svg-icons": "^6.2.1",
"@fortawesome/free-brands-svg-icons": "^7.1.0",
"@fortawesome/free-regular-svg-icons": "^6.2.1",
"@fortawesome/free-solid-svg-icons": "^6.2.1",
"@fortawesome/react-fontawesome": "^0.2.0",
"@fortawesome/react-fontawesome": "^3.1.1",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

FontAwesome 7.1.0 free-brands-svg-icons compatibility fontawesome-svg-core 6

💡 Result:

Short answer: No — @fortawesome/free-brands-svg-icons@7.1.0 is part of Font Awesome v7 and expects the v7 SVG core; it is not intended to be used with @fortawesome/fontawesome-svg-core v6. Upgrade your fontawesome-svg-core to v7 to match the icon package. [1][2]

Sources:

  • Font Awesome v7 upgrade / package docs. [1]
  • @fortawesome/free-brands-svg-icons package listing (v7.x). [2]

🌐 Web query:

react-fontawesome 3.1.1 peer dependencies fontawesome-svg-core version

💡 Result:

@fortawesome/react-fontawesome v3.1.1 lists @fortawesome/fontawesome-svg-core as a peer dependency; the package is compatible with Font Awesome core v6 (and v7 per the repo compatibility notes) — common peer-range seen is "~1 || ~6" (i.e. v6.x is supported). [1][2]

Sources:

  • package info showing peerDependencies (jsDocs/npm metadata). [1]
  • GitHub compatibility notes (react-fontawesome v3.x supports FontAwesome core 6.x and 7.x). [2]

Upgrade @fortawesome/fontawesome-svg-core to v7 to match @fortawesome/free-brands-svg-icons@7.1.0.

@fortawesome/free-brands-svg-icons@7.1.0 requires @fortawesome/fontawesome-svg-core v7, but the current version is 6.2.1. This incompatibility will cause runtime issues. Align all FontAwesome packages to v7.

🤖 Prompt for AI Agents
In `@package.json` around lines 17 - 21, The package
`@fortawesome/fontawesome-svg-core` is pinned to 6.2.1 but
`@fortawesome/free-brands-svg-icons` is 7.1.0; update
`@fortawesome/fontawesome-svg-core` to a v7 range (e.g., ^7.0.0 or ^7.1.0) and
align the other FontAwesome packages (e.g., `@fortawesome/free-regular-svg-icons`,
`@fortawesome/free-solid-svg-icons`, `@fortawesome/react-fontawesome`) to compatible
v7 releases so all fontawesome packages use the same major version; after
updating the package.json entry names (e.g.,
"@fortawesome/fontawesome-svg-core": "^7.x"), run your package manager install
to refresh lockfiles and test for runtime/import issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant