fix: update broken links to moved community governance docs #4878
Conversation
Sourya07
requested review from
Mayaleeeee,
TRohit20,
akshatnema,
anshgoyalevil,
asyncapi-bot-eve,
derberg,
princerajpoot20,
sambhavgupta0705 and
thulieblack
as code owners
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThis PR updates many Markdown and React component hyperlinks to point from root-level or old repository paths to reorganized Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ 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)
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. Comment |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4878--asyncapi-website.netlify.app/ |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (22)
components/layout/CommunityLayout.tsxmarkdown/about/index.mdmarkdown/blog/2022Q1-summary.mdmarkdown/blog/2023-mentorship-summary.mdmarkdown/blog/2024-Q1-docs-report.mdmarkdown/blog/2024-annual-summary.mdmarkdown/blog/2024-april-summary.mdmarkdown/blog/2024-february-summary.mdmarkdown/blog/2024-july-summary.mdmarkdown/blog/2025-Q1-marketing-report.mdmarkdown/blog/2025-february-summary.mdmarkdown/blog/2025-gsoc-phase-1.mdmarkdown/blog/april-2021-at-asyncapi.mdmarkdown/blog/asyncapi-bounty-program-2024.mdmarkdown/blog/beyond-boundaries.mdmarkdown/blog/first-governance-elections.mdmarkdown/blog/july-december-2021-at-asyncapi.mdmarkdown/blog/march-2021-at-asyncapi.mdmarkdown/blog/new-governance-board.mdpages/community/ambassadors/index.tsxpages/community/board.tsxpages/community/tsc.tsx
🧰 Additional context used
🧠 Learnings (6)
📚 Learning: 2025-11-03T08:14:22.714Z
Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
Learning: In AsyncAPI community blog posts, specifically for conference recaps, the phrase "building boats" is used intentionally and is not a typo. This appeared in the October 2025 community summary blog post (markdown/blog/2025-october-summary.md) in the context of networking at the API Standards booth.
Applied to files:
markdown/blog/april-2021-at-asyncapi.mdmarkdown/blog/2024-february-summary.mdmarkdown/blog/2025-february-summary.mdmarkdown/blog/2024-annual-summary.mdmarkdown/blog/2025-Q1-marketing-report.mdmarkdown/blog/2024-april-summary.md
📚 Learning: 2025-07-19T20:58:34.040Z
Learnt from: bandantonio
Repo: asyncapi/website PR: 4264
File: markdown/docs/tutorials/getting-started/coming-from-openapi.md:24-25
Timestamp: 2025-07-19T20:58:34.040Z
Learning: In the AsyncAPI website documentation, anchor references to specification sections can use camelCase format (e.g., #serverObject, #parameterObject, #messageObject) even if the actual HTML IDs on the spec page use hyphenated lowercase format. This is acceptable and should not be changed.
Applied to files:
markdown/blog/april-2021-at-asyncapi.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:
markdown/blog/2024-Q1-docs-report.md
📚 Learning: 2025-12-29T14:21:28.216Z
Learnt from: sammy200-ui
Repo: asyncapi/website PR: 4804
File: components/navigation/Filter.tsx:32-41
Timestamp: 2025-12-29T14:21:28.216Z
Learning: In the asyncapi/website repository, when you intentionally omit dependencies in React hooks (e.g., useEffect, useMemo), add an eslint-disable comment with an explanatory note above the line to justify the design choice. For example: // eslint-disable-next-line react-hooks/exhaustive-deps: intentionally omitting dependencies to avoid unnecessary re-runs. This helps reviewers understand the rationale and keeps lint guidance informative.
Applied to files:
pages/community/ambassadors/index.tsxcomponents/layout/CommunityLayout.tsxpages/community/tsc.tsxpages/community/board.tsx
📚 Learning: 2025-06-20T14:47:22.389Z
Learnt from: sagarkori143
Repo: asyncapi/website PR: 0
File: :0-0
Timestamp: 2025-06-20T14:47:22.389Z
Learning: The AsyncAPI website modularization PR uses Promise.allSettled for parallel execution of build tasks, which provides better performance and fault isolation compared to sequential execution.
Applied to files:
markdown/blog/asyncapi-bounty-program-2024.md
📚 Learning: 2025-06-10T06:27:25.419Z
Learnt from: aminoxix
Repo: asyncapi/website PR: 4127
File: components/layout/CommunityLayout.tsx:179-179
Timestamp: 2025-06-10T06:27:25.419Z
Learning: In AsyncAPI's community data structure, ambassadors and TSC members are guaranteed to have GitHub accounts. The `github` field is required in both `Ambassador` and `Tsc` interfaces, and the data processing in `addAdditionalUserInfo()` converts GitHub usernames to full URLs, ensuring safe string operations when extracting usernames from URLs.
Applied to files:
pages/community/tsc.tsx
🪛 LanguageTool
markdown/blog/april-2021-at-asyncapi.md
[style] ~35-~35: Use ‘will’ instead of ‘going to’ if the following action is certain.
Context: ... 2.1.0 version of the specification. It is going to be the first release under [open govern...
(GOING_TO_WILL)
markdown/blog/2022Q1-summary.md
[style] ~63-~63: Consider using an alternative to strengthen your wording.
Context: ...rch the implementation. ❤️ If you want to learn more about becoming a meeting ...
(WANT_KEEN)
markdown/blog/2024-april-summary.md
[style] ~44-~44: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...e a new automated TSC voting system! We want to thank [Aayush Saini](https://github.com...
(REP_WANT_TO_VB)
⏰ 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). (4)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
- GitHub Check: Lighthouse CI
🔇 Additional comments (26)
markdown/blog/new-governance-board.md (1)
34-34: Link updates look correct.The links to the Charter and Governance Guide have been properly updated to the new documentation structure (
docs/020-governance-and-policies/). The markdown syntax is correct, and the paths align with the PR description.Since I can only verify this one file from the provided context, I'm unable to confirm whether all other affected files (React components, about page, and additional blog posts mentioned in the PR description) have been consistently updated. The PR states the new links were verified to return 200 OK, so this should be in good shape.
Could you confirm:
- Whether all files referenced in the PR scope (React components in CommunityLayout, Board, TSC, Ambassadors components, the about page, and all blog post markdown files) have been updated with the new link paths?
- Spot-check one of the new links to verify they still return 200 OK (e.g., https://github.com/asyncapi/community/blob/master/docs/020-governance-and-policies/CHARTER.md)?
markdown/blog/2025-gsoc-phase-1.md (1)
40-40: LGTM! Mentorship link correctly updated.The GSoC ideas page link has been properly updated to reflect the new documentation structure under
docs/050-mentorship-program/. This aligns with the broader documentation reorganization across the repository.markdown/blog/july-december-2021-at-asyncapi.md (1)
77-77: LGTM! Historical blog post link updated.The CHARTER.md link has been correctly updated to the new governance docs path. Updating historical blog content ensures readers can still access referenced documentation without encountering 404 errors.
markdown/about/index.md (1)
21-21: LGTM! About page governance link updated.The open governance model link has been correctly updated to point to the new documentation path. This is particularly important since the About page is a key entry point for understanding AsyncAPI's governance structure.
markdown/blog/2024-april-summary.md (1)
44-44: LGTM! Voting documentation link updated.The TSC voting docs link has been correctly updated to the new governance documentation path. This ensures users can access the current voting system documentation without encountering broken links.
pages/community/board.tsx (1)
20-20: LGTM! Governance links correctly updated.All three governance document links have been properly updated to point to the new
docs/020-governance-and-policies/path structure. Verification confirms all links return HTTP 200 and no remaining old-path references exist in the codebase.pages/community/ambassadors/index.tsx (1)
67-67: LGTM! Link updates correctly redirect to new documentation location.The button href updates properly redirect users to the new
AMBASSADOR_PROGRAM.mdlocation within the docs directory structure. These changes resolve the broken links reported in issue #4634.Also applies to: 208-208
markdown/blog/2022Q1-summary.md (1)
63-63: LGTM! Meetings FAQ link correctly updated.The link properly redirects to the new location of the meetings organization documentation within the restructured docs directory.
markdown/blog/april-2021-at-asyncapi.md (1)
35-35: LGTM! Governance charter link correctly updated.The link properly redirects to the new location of the governance charter documentation, maintaining the integrity of the historical blog post reference.
markdown/blog/2024-Q1-docs-report.md (1)
129-129: LGTM! Onboarding checklist link correctly updated.The link properly redirects to the new, more specific location of the onboarding documentation, improving navigation to the correct resource.
markdown/blog/march-2021-at-asyncapi.md (1)
57-57: LGTM! Governance charter link correctly updated.The link properly redirects to the new location of the governance charter documentation, consistent with updates across other blog posts.
markdown/blog/2024-july-summary.md (1)
60-60: LGTM! Link path correctly updated.The TSC voting overview link has been properly migrated to the new governance documentation structure under
docs/020-governance-and-policies/. The markdown syntax is correct.components/layout/CommunityLayout.tsx (1)
267-267: LGTM! Component link correctly updated.The TSC membership documentation link in the QuestionCard component has been properly updated to point to the new governance documentation structure. The change is consistent with the broader documentation migration effort.
markdown/blog/2025-Q1-marketing-report.md (1)
101-101: LGTM! Strategy document link properly migrated.The 2025 marketing strategy link has been correctly updated to the new documentation structure under
docs/030-project-vision-strategy-goals/. This aligns with the broader effort to organize documentation by category.markdown/blog/2024-february-summary.md (2)
16-16: LGTM! GSoC ideas page link correctly updated.The Google Summer of Code ideas page link has been properly updated to the mentorship program documentation structure under
docs/050-mentorship-program/. The path structure is consistent with the documentation reorganization.
48-48: LGTM! Working groups documentation link migrated correctly.The Working Groups documentation link has been properly updated to the governance structure under
docs/020-governance-and-policies/. This change aligns with the overall migration of governance-related documents.markdown/blog/2025-february-summary.md (1)
17-17: LGTM! Community goals link correctly updated with anchor preserved.The Community Working Group link has been properly migrated to the new documentation structure under
docs/030-project-vision-strategy-goals/, and the hash fragment for the anchor link is correctly preserved. This ensures users will land on the specific section of the page.markdown/blog/first-governance-elections.md (2)
30-30: ✓ Link update correctly applied with anchor preserved.The GOVERNANCE.md link has been properly updated to the new docs/020-governance-and-policies path, and the #voting anchor is correctly preserved. This aligns with the PR objectives.
24-24: Verify whether TSC_BOARD_MEMBERS.yaml links should have been updated.The file contains three references to
TSC_BOARD_MEMBERS.yaml(lines 24, 58, 122) that still point to the root path athttps://github.com/asyncapi/community/blob/master/TSC_BOARD_MEMBERS.yaml.According to the PR objectives, governance documents were moved to subdirectories (e.g.,
/docs/020-governance-and-policies/). Please confirm whether this YAML file was also relocated as part of the reorganization, or if it intentionally remains at the root level.Also applies to: 58-58, 122-122
markdown/blog/2024-annual-summary.md (1)
172-172: ✓ Link correctly updated to new docs directory structure.The 2025 Community Goals link has been properly moved from the root-level
annual-goals/directory to the consolidateddocs/030-project-vision-strategy-goals/path, aligning with the PR's restructuring objectives.markdown/blog/asyncapi-bounty-program-2024.md (1)
35-35: ✓ Both governance process links correctly updated.The two governance/voting documentation links have been properly updated to the new
docs/020-governance-and-policies/paths. This maintains consistency across the PR's link restructuring and correctly reflects the voting process automation changes described in the surrounding text.pages/community/tsc.tsx (3)
30-30: TSC membership documentation link is accessible. The URL returns a 200 OK response and correctly points to the governance documentation path.
45-45: Governance charter link is correctly configured and accessible.The URL points to the governance documentation and returns HTTP 200, confirming it is accessible. The link is properly implemented with appropriate test attributes.
30-45: No issues found. All governance documentation links in the codebase already follow the consistent pattern with thedocs/020-governance-and-policies/path structure (confirmed acrosspages/community/tsc.tsx,pages/community/board.tsx, and markdown files). No old-pattern links remain.markdown/blog/beyond-boundaries.md (1)
40-40: GitHub documentation links are accessible. Both URLs return HTTP 200 and are properly configured.markdown/blog/2023-mentorship-summary.md (1)
82-84: No issues found with the GSoC ideas page links. The URL is accessible (HTTP 200), and both project anchors (#2-script-stability-enhancement-for-asyncapi-website and #5-asyncapi-website-ui-kit-development) correctly reference existing headers in the GSoC ideas documentation. The links are properly formatted and functional.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4878 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 796 796
Branches 146 146
=========================================
Hits 796 796 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@Sourya07 can you please have a look at the coderabbit's suggestion |
|
@princerajpoot20 okay sir 👍 |
asyncapi-bot
requested review from
CBID2,
bandantonio,
devilkiller-ag and
vishvamsinh28
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @markdown/blog/july-2023.md:
- Line 16: The paragraph contains an empty markdown link "approved]()" which
breaks validation; fix it by either inserting the correct URL for the approved
budget (replace the empty parentheses after "approved") or remove the markdown
link and leave plain text "approved" (update the sentence that currently
contains "approved]()"). Ensure the final sentence reads correctly and the
markdown link is not left empty.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (3)
markdown/blog/2023-summary.mdmarkdown/blog/asyncapi-ambassador-program.mdmarkdown/blog/july-2023.md
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
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.
📚 Learning: 2025-11-03T08:14:22.714Z
Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
Learning: In AsyncAPI community blog posts, specifically for conference recaps, the phrase "building boats" is used intentionally and is not a typo. This appeared in the October 2025 community summary blog post (markdown/blog/2025-october-summary.md) in the context of networking at the API Standards booth.
Applied to files:
markdown/blog/2023-summary.mdmarkdown/blog/july-2023.md
📚 Learning: 2025-06-10T06:27:25.419Z
Learnt from: aminoxix
Repo: asyncapi/website PR: 4127
File: components/layout/CommunityLayout.tsx:179-179
Timestamp: 2025-06-10T06:27:25.419Z
Learning: In AsyncAPI's community data structure, ambassadors and TSC members are guaranteed to have GitHub accounts. The `github` field is required in both `Ambassador` and `Tsc` interfaces, and the data processing in `addAdditionalUserInfo()` converts GitHub usernames to full URLs, ensuring safe string operations when extracting usernames from URLs.
Applied to files:
markdown/blog/asyncapi-ambassador-program.md
🪛 markdownlint-cli2 (0.18.1)
markdown/blog/july-2023.md
16-16: No empty links
(MD042, no-empty-links)
⏰ 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). (3)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
🔇 Additional comments (4)
markdown/blog/july-2023.md (1)
16-16: Mentorship program link update looks correct.The mentorship program hyperlink now points to the updated docs path (
docs/050-mentorship-program/asyncapi-mentorship-README.md), aligning with the repository reorganization. Syntax is valid.markdown/blog/2023-summary.md (1)
158-158: Mentorship program link update is correct.Line 158 properly updates the AsyncAPI Mentorship Program II link to the new docs path (
docs/050-mentorship-program/asyncapi-mentorship-README.md). Markdown syntax is valid and the link follows the repository reorganization scheme.markdown/blog/asyncapi-ambassador-program.md (2)
1-61: Inconsistency between AI summary and code changes.The AI-generated summary states "Updated two link targets in the ambassador program section," but only one changed line (line 51) is marked with a
~indicator in the annotated code. The second link mentioned in the summary is unclear. Please clarify whether there are additional link updates that should be reviewed or if the summary is inaccurate.
51-51: No issues found. The link toAMBASSADORS_MEMBERS.yamlcorrectly points to the repository root of asyncapi/community, which is the actual file location.
|
@princerajpoot20 all done 👍 |
markdown/blog/july-2023.md
Outdated
| --- | ||
|
|
||
| Earlier this month, we officially kickstarted the AsyncAPI Mentorship Program. After receiving an overwhelming response of over 90+ applications for the program, we inducted [13 mentees into the AsyncAPI mentorship program](https://github.com/asyncapi/community/tree/master/mentorship/asyncapi-mentorship/2023). We are thrilled to welcome these talented individuals and look forward to seeing them grow and excel in their respective projects. Additionally, we are excited that our [budget of $19,500 for the AsyncAPI Mentorship Program got approved](), which means we can compensate all successful mentees of the program. We are grateful for the support and look forward to a successful program. | ||
| Earlier this month, we officially kickstarted the AsyncAPI Mentorship Program. After receiving an overwhelming response of over 90+ applications for the program, we inducted [13 mentees into the AsyncAPI mentorship program](https://github.com/asyncapi/community/blob/master/docs/050-mentorship-program/asyncapi-mentorship-README.md). We are thrilled to welcome these talented individuals and look forward to seeing them grow and excel in their respective projects. Additionally, we are excited that our budget of $19,500 for the AsyncAPI Mentorship Program got approved, which means we can compensate all successful mentees of the program. We are grateful for the support and look forward to a successful program. |
There was a problem hiding this comment.
@thulieblack The reference link is missing in the blog. Could you help us by providing that reference
There was a problem hiding this comment.
I searched through the community repository but couldn’t find this link .
There was a problem hiding this comment.
There's a folder for mentorships look there
There was a problem hiding this comment.
I couldn’t find any existing documentation that mentions a $19,500 budget for the AsyncAPI Mentorship Program.
There was a problem hiding this comment.
reference: https://github.com/orgs/asyncapi/discussions/689#discussioncomment-6028934
cc: @thulieblack I am also not able to locate that. The closest reference to budget approval is this one. should we go ahead with this?
@Sourya07 as I mentioned earlier, when changing a link, you should point it to the correct file and not an incorrect one.
Don’t you think your “13 selected mentees” reference is pointing to the wrong file? It should be:
https://github.com/asyncapi/community/blob/master/docs/050-mentorship-program/asyncapi-mentorship-2023-project-ideas.md
|
@Sourya07 good work. Just make sure you have verified that all the links are working and that they are the same as the original previous references |
okay i will re-verify once more wait for merge call |
|
@princerajpoot20 once confirm this, show i can proceed . |
|
yes |
done |
markdown/blog/beyond-boundaries.md
Outdated
| We knew piloting an in-house mentorship program would be challenging, so we made the initial program a way to collect feedback. We approached the program flexibly, avoiding rigid decisions or commitments. | ||
|
|
||
| During the project ideas phase, [we received 19 project ideas](https://github.com/asyncapi/community/blob/master/mentorship/asyncapi-mentorship/2022/project-ideas.md), and [ten of these projects made it to the final phase](https://github.com/asyncapi/community/blob/master/mentorship/asyncapi-mentorship/2022/README.md) but out of the ten selected candidates for the program only [six](https://github.com/orgs/asyncapi/discussions/577) were able to complete their project. This program addresses the real needs of the open-source community. It ensures the program leaders forge meaningful relationships with the participants to ensure their diverse voices are heard and provide them with resources, advice, and networking opportunities. | ||
| During the project ideas phase, [we received 19 project ideas](https://github.com/asyncapi/community/blob/master/docs/050-mentorship-program/asyncapi-mentorship-2022-project-ideas.md), and [ten of these projects made it to the final phase](https://github.com/asyncapi/community/blob/master/docs/050-mentorship-program/asyncapi-mentorship-2023-project-ideas.md) but out of the ten selected candidates for the program only [six](https://github.com/orgs/asyncapi/discussions/577) were able to complete their project. This program addresses the real needs of the open-source community. It ensures the program leaders forge meaningful relationships with the participants to ensure their diverse voices are heard and provide them with resources, advice, and networking opportunities. |
There was a problem hiding this comment.
Please be attentive and see what changes you are making. If the reference is from 2022, then why would we give a 2023 link?
Before making changes to the link, please read the docs to get the context. Then you will be able to easily understand which document it should point to.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @markdown/blog/july-2023.md:
- Line 16: In the July blog post paragraph that currently reads
"approved(https://github.com/orgs/asyncapi/discussions/689#discussioncomment-6028934)",
fix the markdown link by wrapping the link text in brackets so it becomes
"[approved](https://github.com/orgs/asyncapi/discussions/689#discussioncomment-6028934)";
update the string in markdown/blog/july-2023.md (the sentence mentioning the
$19,500 budget) accordingly to produce a proper clickable hyperlink.
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/july-2023.md
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
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.
📚 Learning: 2025-11-03T08:14:22.714Z
Learnt from: thulieblack
Repo: asyncapi/website PR: 4512
File: markdown/blog/2025-october-summary.md:37-37
Timestamp: 2025-11-03T08:14:22.714Z
Learning: In AsyncAPI community blog posts, specifically for conference recaps, the phrase "building boats" is used intentionally and is not a typo. This appeared in the October 2025 community summary blog post (markdown/blog/2025-october-summary.md) in the context of networking at the API Standards booth.
Applied to files:
markdown/blog/july-2023.md
🪛 markdownlint-cli2 (0.18.1)
markdown/blog/july-2023.md
16-16: Bare URL used
(MD034, no-bare-urls)
⏰ 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). (3)
- GitHub Check: Redirect rules - asyncapi-website
- GitHub Check: Header rules - asyncapi-website
- GitHub Check: Pages changed - asyncapi-website
princerajpoot20
left a comment
princerajpoot20
left a comment
There was a problem hiding this comment.
LGTM! Thanks for your contribution
👍 |
|
@thulieblack @TRohit20 PTAL |
|
Another broken link: Both URLs return “This store is unavailable”. Found via: The Swag Store link should be updated or removed if the store is no longer active. |
5 participants
Description
Ambassadors) andaboutpage.markdown/blog/*.md).asyncapi/community(likeCHARTER.md,GOVERNANCE.md,TSC_MEMBERSHIP.md) which have been moved to subdirectories (e.g.,/docs/020-governance-and-policies/).Related issue(s)
Fixes [BUG] Broken Links in Documentation – Open Governance Model and Link - Redirects to 404 #4634
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.