chore(blog): add last summary of the year #3463
Conversation
thulieblack
requested review from
quetzalliwrites,
derberg,
akshatnema,
magicmatatjahu,
anshgoyalevil,
Mayaleeeee and
asyncapi-bot-eve
as code owners
WalkthroughA new markdown file titled "November and December Community Update And AsyncAPI Conf in Paris 2024" has been created, detailing community activities and reflections, including a summary of the AsyncAPI Conference held in Paris. Additionally, the existing October summary document has been updated to reflect recent events, community goals, and conference details. Both documents emphasize community engagement and upcoming initiatives. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
Documentation and Community
|
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
asyncapi-bot
requested review from
devilkiller-ag,
sambhavgupta0705,
BhaswatiRoy,
J0SAL,
TRohit20 and
VaishnaviNandakumar
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3463 +/- ##
=======================================
Coverage 86.59% 86.59%
=======================================
Files 21 21
Lines 664 664
=======================================
Hits 575 575
Misses 89 89 ☔ View full report in Codecov by Sentry. |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-3463--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: 0
🧹 Outside diff range and nitpick comments (1)
markdown/blog/2024-december-and-paris.md (1)
13-13: Consider enhancing the excerpt for better SEO and readability.The current excerpt is quite similar to the title and could be more descriptive. Consider adding key highlights or takeaways from the post.
-excerpt: 'November and December Community Update And Paris Conference Summary' +excerpt: 'Highlights from AsyncAPI Conference in Paris, community achievements, and welcoming new TSC members as we wrap up an eventful 2024'
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
📒 Files selected for processing (2)
markdown/blog/2024-december-and-paris.md(1 hunks)markdown/blog/2024-october-summary.md(0 hunks)
💤 Files with no reviewable changes (1)
- markdown/blog/2024-october-summary.md
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-december-and-paris.md
[style] ~27-~27: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.g...
(AWESOME)
[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...
(ENGLISH_WORD_REPEAT_RULE)
🔇 Additional comments (5)
markdown/blog/2024-december-and-paris.md (5)
16-18: LGTM!
The introduction effectively sets the context and tone for the blog post.
130-138: LGTM!
The conclusion effectively wraps up the blog post with appropriate holiday wishes and future plans.
122-128: Verify the GitHub profile link.
Let's ensure the GitHub username is correct and the profile is accessible.
✅ Verification successful
GitHub profile link is valid and matches the name
The GitHub profile ashmit-coder exists and the name matches "Ashmit Jagtap" as specified in the Profiles component.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify GitHub profile exists and matches the name
gh api users/ashmit-coder --jq '.name'
Length of output: 53
🧰 Tools
🪛 LanguageTool
[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...
(ENGLISH_WORD_REPEAT_RULE)
31-35: Verify the existence and accessibility of conference images.
Let's ensure all referenced images exist in the repository.
Also applies to: 39-43, 47-51, 55-59, 63-67, 71-75, 79-83, 87-91, 96-100, 104-108, 112-116
✅ Verification successful
All conference images are present and accessible
All referenced images in the public/img/posts/paris-conf-2024/ directory have been verified to exist, including:
- full-room.webp (referenced in the reviewed snippet)
- All other conference images referenced in lines 39-116
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if all referenced images exist
fd -e webp -p "public/img/posts/paris-conf-2024/" | while read -r img; do
basename=$(basename "$img")
echo "Checking: $basename"
if [ -f "$img" ]; then
echo "✓ Found: $img"
else
echo "✗ Missing: $img"
fi
done
Length of output: 3997
22-23: Verify the PR status and accessibility.
Let's ensure the referenced PR is still open and accessible.
✅ Verification successful
PR link is valid and active
The referenced PR (#1575) in the AsyncAPI Community repository is open and accessible, correctly discussing the 2025 Community Building Goals proposal as mentioned in the blog post.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if the PR is still open and accessible
gh pr view 1575 --repo asyncapi/community --json state,url,title
Length of output: 208
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
markdown/blog/2024-december-and-paris.md (2)
27-27: Consider using more formal language.Consider replacing "amazing" with a more formal alternative like "exceptional" or "outstanding".
🧰 Tools
🪛 LanguageTool
[style] ~27-~27: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.g...(AWESOME)
122-128: Consider renaming the profiles prop.The word "profiles" is repeated in
<Profiles profiles={[...]}. Consider using a more specific prop name or restructuring the component usage.-<Profiles profiles={[ +<Profiles members={[🧰 Tools
🪛 LanguageTool
[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...(ENGLISH_WORD_REPEAT_RULE)
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/2024-december-and-paris.md(1 hunks)
🧰 Additional context used
🪛 LanguageTool
markdown/blog/2024-december-and-paris.md
[style] ~27-~27: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...linkedin.com/in/mehdimedjaoui/) and the amazing team at [APIdays](https://www.apidays.g...
(AWESOME)
[duplication] ~122-~122: Possible typo: you repeated a word
Context: ...oud of the work you have done so far. <Profiles profiles={[ { name: 'Ashmit Jagtap', a...
(ENGLISH_WORD_REPEAT_RULE)
🔇 Additional comments (5)
markdown/blog/2024-december-and-paris.md (5)
1-15: LGTM! Frontmatter is well-structured and complete.
The metadata follows the correct format and includes all necessary fields.
16-19: LGTM! Introduction effectively sets context.
The introduction provides clear context and appropriately addresses the timing of the post.
130-138: LGTM! Conclusion provides appropriate closure.
The conclusion effectively wraps up the post and sets expectations for future content.
20-24: Verify the referenced PR link.
The section effectively encourages community participation in the 2025 goals discussion.
✅ Verification successful
PR link is valid and active
The referenced PR #1575 in the AsyncAPI Community repository exists, is currently open, and correctly relates to the "AsyncAPI Community Building Goals 2025 Proposal" as mentioned in the blog post.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify if the referenced PR exists and is accessible
gh pr view 1575 --repo asyncapi/community --json url,state,title
Length of output: 208
31-116: Verify all conference images are present in the repository.
The conference section uses multiple images that should be verified.
✅ Verification successful
All conference images are present and correctly referenced
All 11 conference images referenced in the blog post are present in the expected location at public/img/posts/paris-conf-2024/.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Check if all referenced conference images exist
for img in full-room.webp lukasz-and-fran.webp naresh-and-pierre.webp frank.webp leonid.webp hugo.webp julien-and-alessandro.webp annegret.webp jonathan.webp hari-and-joel.webp laurent-and-hugo.webp; do
if [ -f "public/img/posts/paris-conf-2024/$img" ]; then
echo "✓ Found: $img"
else
echo "✗ Missing: $img"
fi
done
Length of output: 3577
|
Testing workflow is failing due to some codecov error. Raised a possible hot fix PR for the same. |
|
/rtm |
Last blog of the year including Paris highlights and some community updates
Summary by CodeRabbit
New Features
Bug Fixes
Documentation