Skip to content

Conversation

@HDJadeja
Copy link

@HDJadeja HDJadeja commented Sep 4, 2025

Fix broken FAQ link on Events page

Description

This PR fixes the broken "Read FAQ" link on the Events page
.
The link was previously pointing to a non-existent path in the community repo:

https://github.com/asyncapi/community/blob/master/MEETINGS_ORGANIZATION.md

It now correctly points to:

https://github.com/asyncapi/community/blob/master/docs/060-meetings-and-communication/MEETINGS_ORGANIZATION.md

Related issue(s)

Resolves #4382

Summary by CodeRabbit

  • Documentation
    • Updated the “Meetings organization” link on the Community Events page to the current documentation location, improving accuracy and navigation.
    • Prevents users from landing on an outdated path or potential 404s.
    • No changes to page layout, interactions, or functionality; only the link destination was updated.

FIXED the broken link of  FAQ  PAGE
@netlify
Copy link

netlify bot commented Sep 4, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 1e9de46
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/68b94275f2cb770008463d33
😎 Deploy Preview https://deploy-preview-4383--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 4, 2025

Walkthrough

Updates the "Read FAQ" link on the community events page to point to a new GitHub path under docs/060-meetings-and-communication/MEETINGS_ORGANIZATION.md. No other content, logic, or exported entities are changed.

Changes

Cohort / File(s) Summary
Community Events Page link update
pages/community/events/index.tsx
Changed TextLink href from .../MEETINGS_ORGANIZATION.md to .../docs/060-meetings-and-communication/MEETINGS_ORGANIZATION.md; no other modifications.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Assessment against linked issues

Objective Addressed Explanation
Fix broken FAQ link on Events page to a valid destination (#4382)

Suggested labels

ready-to-merge

Suggested reviewers

  • derberg
  • akshatnema
  • anshgoyalevil
  • Mayaleeeee
  • asyncapi-bot-eve
  • sambhavgupta0705

Poem

I hopped through links with whiskers keen,
Found a 404—oh what a scene!
A twitch, a tap, the path made right,
Now FAQs sparkle, clear and bright.
Thump-thump! The trail’s anew—
Carrots for commits, and docs that view. 🥕✨


📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3a77b6b and 1e9de46.

📒 Files selected for processing (1)
  • pages/community/events/index.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Test NodeJS PR - windows-latest
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Lighthouse CI
✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

@codecov
Copy link

codecov bot commented Sep 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (3a77b6b) to head (1e9de46).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4383   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          778       778           
  Branches       144       144           
=========================================
  Hits           778       778           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@HDJadeja HDJadeja changed the title Update index.tsx fix(events): update broken FAQ link on Events page Sep 4, 2025
@asyncapi-bot
Copy link
Contributor

⚡️ Lighthouse report for the changes in this PR:

Category Score
🔴 Performance 35
🟢 Accessibility 98
🟢 Best practices 92
🟢 SEO 100
🔴 PWA 33

Lighthouse ran on https://deploy-preview-4383--asyncapi-website.netlify.app/

@HDJadeja
Copy link
Author

HDJadeja commented Sep 4, 2025

Hi maintainers,
The failing Cypress test on the macOS runner seems to be due to a corrupted download during CI setup (network or proxy issue).
This issue appears unrelated to my PR, which only fixes a broken link on the Events page.
Please let me know if you'd like me to take any further action. Thanks!

setup and automation&nbsp;
<TextLink
href='https://github.com/asyncapi/community/blob/master/MEETINGS_ORGANIZATION.md'
href='https://github.com/asyncapi/community/blob/master/docs/060-meetings-and-communication/MEETINGS_ORGANIZATION.md'
Copy link
Member

Choose a reason for hiding this comment

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

I would say we should extract these constant values. I see there are other similar issues with incorrect paths like #4384 . My suggestion would be to have a constants file with all these paths in one place.

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.

[BUG] Broken FAQ link on Events page leads to 404 on GitHub

3 participants