docs: fix broken community repository links

[sammy200-ui]

Changes Made

• Updated Slack Etiquette links from /slack-etiquette.md to /docs/060-meetings-and-communication/slack-etiquette.md
• Updated Git Workflow links from /documents/git-workflow.md to /docs/010-contribution-guidelines/git-workflow.md
• Updated Recognize Contributors link from /recognize-contributors.md to /docs/010-contribution-guidelines/recognize-contributors.md
• Fixed internal anchor link in reply-info.md from #multiple-channels-with-single-message to #multiple-channels-with-single-message-when-reply-address-is-known

Related Issue

Closes #4589

Summary by CodeRabbit

• Documentation
  • Updated multiple documentation links to new canonical docs locations (contribution, Git workflow, contributor recognition).
  • Repointed Slack etiquette references to the centralized docs.
  • Added guidance in the GSOD post to identify mentees, mentors, ideas, and matching details.
  • Fixed internal anchors and README links for more accurate navigation.

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

[coderabbitai]

Walkthrough

This PR fixes multiple broken documentation links across the repo (Slack etiquette, Git workflow, recognize-contributors) and updates one internal anchor target; one blog post also adds four Slack-channel bullets.

Changes

Cohort / File(s)	Summary
Blog posts: Slack link + content markdown/blog/google-season-of-docs-2022.md, markdown/blog/may-2021-at-asyncapi.md, markdown/blog/openforce-2022.md	Replaced Slack etiquette links from /slack-etiquette.md to /docs/community/060-meetings-and-communication/slack-etiquette (docs path). Added four new bullets for mentees/mentors/ideas/matching in google-season-of-docs-2022.md.
Contribution & README links CONTRIBUTING.md, README.md	Updated Git workflow and recognize-contributors/All Contributors links to point to the AsyncAPI docs site paths (www.asyncapi.com/docs/... or /docs/...) instead of previous repo paths.
Docs anchor update markdown/docs/concepts/asyncapi-document/reply-info.md	Changed internal anchor target from #multiple-channels-with-single-message to #multiple-channels-with-single-message-when-reply-address-is-known.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Focus review on link targets and one anchor change.
• Check google-season-of-docs-2022.md additions for formatting and intent.

Possibly related PRs

• fix: broken AsyncAPI contributing guidelines link (#4395) #4398 — edits documentation links and CONTRIBUTING.md references (similar link corrections).
• docs: fix broken git-workflow.md links across repository #4585 — updates broken git-workflow links in CONTRIBUTING/README (direct overlap).
• docs(community): update latest community documentation #4432 — adjusts docs path routing and community guidance links (related link migration).

Suggested labels

ready-to-merge

Suggested reviewers

• derberg
• bandantonio
• thulieblack
• akshatnema
• TRohit20

Poem

🐰 I hopped through docs with eager paws,
I fixed the paths and healed the flaws.
From Slack to guides the links now sing,
Anchors set — let clarity spring! 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR addresses most requirements from issue #4589 but notably fails to handle the Code of Conduct Committee link verification and uses website URLs instead of the specified GitHub community repository paths.	Complete the verification of the Code of Conduct Committee link in CODE_OF_CONDUCT.md as specified in issue #4589, and align link destinations with the issue requirements (GitHub community repo paths vs. live website URLs).

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: fix broken community repository links' accurately summarizes the main change—updating broken documentation links throughout the repository.
Out of Scope Changes check	✅ Passed	The PR includes an additional internal anchor link fix in reply-info.md that was not mentioned in issue #4589, though it is documentation-related and beneficial.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3ceb525 and 4c67e8a.

📒 Files selected for processing (5)

• CONTRIBUTING.md (3 hunks)
• README.md (1 hunks)
• markdown/blog/google-season-of-docs-2022.md (1 hunks)
• markdown/blog/may-2021-at-asyncapi.md (1 hunks)
• markdown/blog/openforce-2022.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (2)

• markdown/blog/google-season-of-docs-2022.md
• markdown/blog/may-2021-at-asyncapi.md

🧰 Additional context used

🧠 Learnings (4)

📓 Common learnings

Learnt from: asyncapi-bot
Repo: asyncapi/website PR: 0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch

📚 Learning: 2025-02-18T12:07:42.211Z

Learnt from: asyncapi-bot
Repo: asyncapi/website PR: 0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch

Applied to files:

• CONTRIBUTING.md

📚 Learning: 2024-10-09T17:35:36.557Z

Learnt from: akshatnema
Repo: asyncapi/website PR: 3265
File: tests/fixtures/toolsObjectData.js:51-52
Timestamp: 2024-10-09T17:35:36.557Z
Learning: When reviewing code in the 'asyncapi/website' repository, akshatnema prefers that I do not provide committable code suggestions.

Applied to files:

• CONTRIBUTING.md

📚 Learning: 2025-01-19T04:51:41.255Z

Learnt from: anshgoyalevil
Repo: asyncapi/website PR: 3557
File: tests/fixtures/markdown/check-edit-links-data.js:3-11
Timestamp: 2025-01-19T04:51:41.255Z
Learning: In the AsyncAPI website repository, the test data in `tests/fixtures/markdown/check-edit-links-data.js` intentionally includes inconsistent paths (with and without 'docs' prefix) to verify the script's ability to normalize and handle ambiguous path structures.

Applied to files:

• README.md

🪛 LanguageTool

README.md

[uncategorized] ~47-~47: Possible missing comma found.
Context: ... place of <username>. For multiple contributions it is recommended to have [proper confi...

(AI_HYDRA_LEO_MISSING_COMMA)

⏰ 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). (2)

• GitHub Check: cypress-run
• GitHub Check: Test NodeJS PR - windows-latest

🔇 Additional comments (6)

README.md (1)

47-47: Link update aligns with PR objectives.

The Git workflow link correctly points to the live documentation site (https://www.asyncapi.com/docs/community/010-contribution-guidelines/git-workflow) rather than a raw GitHub markdown file, matching the PR's intent to centralize contributor guidance to the AsyncAPI docs site.

markdown/blog/openforce-2022.md (1)

34-34: Slack etiquette link correctly updated to docs site.

The link now points to the live documentation (https://www.asyncapi.com/docs/community/060-meetings-and-communication/slack-etiquette), making it easier for OpenForce participants and other community members to access the policy directly from the official docs.

CONTRIBUTING.md (4)

52-52: Slack etiquette link updated correctly (line 52).

Link now points to the live docs site (https://www.asyncapi.com/docs/community/060-meetings-and-communication/slack-etiquette), properly guiding contributors to etiquette guidelines during the community engagement section.

---

62-62: Git workflow link correctly updated (line 62).

The link now directs to the official docs (https://www.asyncapi.com/docs/community/010-contribution-guidelines/git-workflow), making the workflow guidance accessible from the live website rather than a raw GitHub file.

---

87-87: Recognize-contributors link properly updated (line 87).

The link now points to the live documentation site (https://www.asyncapi.com/docs/community/010-contribution-guidelines/recognize-contributors), correctly directing contributors to the contribution recognition guidelines.

---

52-87: All three documentation URLs resolve correctly and return relevant content.

The web search verification confirms that each of the three updated links in CONTRIBUTING.md is accessible and returns appropriate documentation:

• slack-etiquette: Returns AsyncAPI's Slack etiquette guidance ✓
• git-workflow: Returns AsyncAPI's git workflow documentation ✓
• recognize-contributors: Returns contributor recognition guidelines ✓

The URLs follow the established asyncapi.com/docs/community/ pattern and are fully functional. No broken links or access issues were detected.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	e6d3a24
🔍 Latest deploy log	https://app.netlify.com/projects/asyncapi-website/deploys/693f8a3962aea4000800c685
😎 Deploy Preview	https://deploy-preview-4600--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (9c3dcd6) to head (e6d3a24).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4600   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          799       799           
  Branches       146       146           
=========================================
  Hits           799       799           

☔ 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.

[sammy200-ui]

@princerajpoot20 @bandantonio pr is raised , you can review it

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

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

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

[princerajpoot20]

What is the reason behind making this change?

[sammy200-ui]

@princerajpoot20 The anchor link was broken because it was incomplete.

checkout this headline
Multiple channels with single message when reply address is known

So the anchor ID should be #multiple-channels-with-single-message-when-reply-address-is-known (matching the full heading).

The old link #multiple-channels-with-single-message was missing the -when-reply-address-is-known part, causing it to not work when clicked. You can verify this by checking the live URL:
https://www.asyncapi.com/docs/concepts/asyncapi-document/reply-info#multiple-messages-over-the-same-channel-when-reply-address-is-known

The link in the "Multiple messages over the same channel when reply address is known" section should properly reference the section above it.

[sammy200-ui]

hello @princerajpoot20 , just a follow-up on this PR

[princerajpoot20]

LGTM!

[princerajpoot20]

PTAL @TRohit20 @bandantonio

[sammy200-ui]

update on pr would be nice @bandantonio @TRohit20

[thulieblack]

@sammy200-ui please link the docs the one on the website not to the .md files

[sammy200-ui]

hello @thulieblack
Just to confirm - do you want me to change the links from GitHub markdown files to the live website URLs?

For example, change:
https://github.com/asyncapi/community/blob/master/docs/060-meetings-and-communication/slack-etiquette.md

To something like:
https://www.asyncapi.com/community/slack-etiquette

[thulieblack]

Yes exactly

[sammy200-ui]

@thulieblack please have a look, let me know if there are any other changes thats need to done

[sammy200-ui]

@thulieblack thanks for approval

[sammy200-ui]

Hi! @thulieblack @bandantonio
Just wanted to kindly follow up on this PR. It was approved about a weeks ago, so I wanted to check if there’s anything else needed from my side before it can be merged.
Happy to make any additional changes if required. Thanks!

[bandantonio]

/rtm

[asyncapi-bot]

Hello, @bandantonio! 👋🏼
This PR is not up to date with the base branch and can't be merged.
Please update your branch manually with the latest version of the base branch.
PRO-TIP: To request an update from the upstream branch, simply comment /u or /update and our bot will handle the update operation promptly.

       The only requirement for this to work is to enable [Allow edits from maintainers](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork) option in your PR. Also the update will not work if your fork is located in an organization, not under your personal profile.
       Thanks 😄

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[sammy200-ui]

@bandantonio is the branch not up to date , thats why its failing ?

[thulieblack]

/rtm

[sammy200-ui]

@princerajpoot20 Just wanted to kindly follow up on this PR. It was approved about a two weeks ago, so I wanted to check if there’s anything else needed from my side before it can be merged.

[princerajpoot20]

@sammy200-ui
Umm… it’s currently blocked because our pipeline has been flaky since December 5.
I’ve just re-run the pipeline—hopefully it should work now.
However, it has been flaky for quite a long time and needs a permanent fix.

@Shriya-Chauhan is looking into it. I’ll get in touch with her again to check on the status.

[princerajpoot20]

re-run worked!

[princerajpoot20]

/rtm