Skip to content

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Jun 20, 2025

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Added a new "Marketing WG Meeting" scheduled for June 24, 2025.
    • Added a new video entry for the "AsyncAPI Design WG Meeting, Tuesday June 17th 2025".
  • Chores

    • Removed the "AsyncAPI Community Working Group Meeting" dated March 11, 2025.
    • Removed the "GSoC Welcome Contributors Call | May 29th 2025" video entry.

@netlify
Copy link

netlify bot commented Jun 20, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 568d593
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/6854ad9eb429e40008f5c8bc
😎 Deploy Preview https://deploy-preview-4195--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 Jun 20, 2025

Walkthrough

The changes update two JSON configuration files: one meeting entry was removed and a new meeting was added in meetings.json, while in newsroom_videos.json, an old video entry was removed and a new one was inserted at the beginning of the list. No other modifications were made.

Changes

File(s) Change Summary
config/meetings.json Removed the earliest "AsyncAPI Community Working Group Meeting" (2025-03-11); added "Marketing WG Meeting" (2025-06-24) at the end.
config/newsroom_videos.json Added new "AsyncAPI Design WG Meeting, Tuesday June 17th 2025" video at the start; removed last "GSoC Welcome Contributors Call

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

  • derberg
  • akshatnema
  • magicmatatjahu
  • anshgoyalevil
  • Mayaleeeee
  • devilkiller-ag
  • sambhavgupta0705
  • asyncapi-bot-eve

Poem

In the garden of data, I hop and I prune,
Old meetings and videos, retired too soon.
New entries now bloom, with a digital cheer,
Keeping the schedule and news ever clear.
🐇✨
Hop, hop, update—see you next year!


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.
    • Explain this complex logic.
    • 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. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • 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 src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai 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.

Documentation and Community

  • 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
Contributor

@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

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d2a9a78 and 568d593.

📒 Files selected for processing (2)
  • config/meetings.json (1 hunks)
  • config/newsroom_videos.json (1 hunks)
⏰ Context from checks skipped due to timeout of 180000ms (8)
  • GitHub Check: Automerge PR autoapproved by a bot
  • 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 - ubuntu-latest
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
config/meetings.json (1)

155-162: New meeting entry appended in correct chronological order
The “Marketing WG Meeting” for 2025-06-24 is inserted after the 2025-06-19 Design WG meeting, with all required fields present and JSON syntax valid.

Comment on lines +2 to +7
{
"image_url": "https://i.ytimg.com/vi/0srKJiLCIUc/hqdefault.jpg",
"title": "AsyncAPI Design WG Meeting, Tuesday June 17th 2025",
"description": "https://github.com/asyncapi/community/issues/1935.",
"videoId": "0srKJiLCIUc"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Mismatch between video title and issue link
The new entry’s title refers to the “AsyncAPI Design WG Meeting, Tuesday June 17th 2025” but the description URL points to issue #1935 (Community WG Meeting). It should reference the Design WG issue #1955 instead.

Proposed fix:

   {
-    "image_url": "https://i.ytimg.com/vi/0srKJiLCIUc/hqdefault.jpg",
-    "title": "AsyncAPI Design WG Meeting, Tuesday June 17th 2025",
-    "description": "https://github.com/asyncapi/community/issues/1935.",
+    "image_url": "https://i.ytimg.com/vi/0srKJiLCIUc/hqdefault.jpg",
+    "title": "AsyncAPI Design WG Meeting, Tuesday June 17th 2025",
+    "description": "https://github.com/asyncapi/community/issues/1955.",
     "videoId": "0srKJiLCIUc"
   },
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{
"image_url": "https://i.ytimg.com/vi/0srKJiLCIUc/hqdefault.jpg",
"title": "AsyncAPI Design WG Meeting, Tuesday June 17th 2025",
"description": "https://github.com/asyncapi/community/issues/1935.",
"videoId": "0srKJiLCIUc"
},
{
"image_url": "https://i.ytimg.com/vi/0srKJiLCIUc/hqdefault.jpg",
"title": "AsyncAPI Design WG Meeting, Tuesday June 17th 2025",
"description": "https://github.com/asyncapi/community/issues/1955.",
"videoId": "0srKJiLCIUc"
},
🤖 Prompt for AI Agents
In config/newsroom_videos.json around lines 2 to 7, the description URL for the
video entry incorrectly points to issue #1935 (Community WG Meeting) while the
title refers to the Design WG Meeting on June 17th, 2025. Update the description
URL to reference the correct Design WG issue #1955 instead of #1935.

@codecov
Copy link

codecov bot commented Jun 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (d2a9a78) to head (568d593).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4195   +/-   ##
=========================================
  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.

@asyncapi-bot asyncapi-bot merged commit 6e24d12 into master Jun 20, 2025
33 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/d2a9a789cb46f0c53d0c1a813243d96d2b133c4c branch June 20, 2025 00:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants