Skip to content

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Mar 26, 2025

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Introduced two upcoming meeting events with detailed schedules, links, and visuals.
    • Added a new video entry showcasing an upcoming community meeting.
  • Chores

    • Removed an outdated video entry for a previous meeting to keep the content current.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 26, 2025

Walkthrough

This pull request updates two JSON configuration files. In meetings.json, two new meeting entries are added with details such as title, calendar link, URL, banner image, and scheduled date. In newsroom_videos.json, a new video entry is introduced at the beginning of the array while an existing video entry has been removed, reflecting an update to the available video content.

Changes

File(s) Change Summary
config/meetings.json Added two new meeting entries: one titled "Preventing API Drift: Ensuring Your APIs Stay True to Their Spec" (with calendar link, URL, banner, and date "2025-04-10T18:00:00.000Z") and one titled "AsyncAPI Community Working Group Meeting" (with corresponding details and date "2025-04-08T15:00:00.000Z").
config/newsroom_videos.json Added a new video entry for "AsyncAPI Community Working Group Meeting, March 25th 2025" (with image, title, description, and videoId) and removed an older video entry for "AsyncAPI Community Working Group Meeting, February 25th 2025".

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

I'm a bunny with a curious code delight,
Hopping through JSON fields both day and night.
Adding meetings and videos with a twitch of my nose,
Leaving behind old entries, as every update shows.
In lines and links my joy does gleam,
Celebrating changes in our data stream!
🐰💻


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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@netlify
Copy link

netlify bot commented Mar 26, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 94e2a36
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67e34bc77ee2d10008ffeb16
😎 Deploy Preview https://deploy-preview-3974--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 site configuration.

@codecov
Copy link

codecov bot commented Mar 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (148ad21) to head (94e2a36).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #3974   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           21        21           
  Lines          667       667           
  Branches       113       113           
=========================================
  Hits           667       667           

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

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: 0

🧹 Nitpick comments (1)
config/meetings.json (1)

72-77: Nitpick: Trailing whitespace in meeting title and date update confirmation.
The "Design WG Meeting " entry (line 73) contains trailing whitespace in the title. Additionally, its date field is updated to "2025-03-20T16:00:00.000Z". Please confirm that the whitespace is intentional and that the revised date correctly reflects the intended schedule.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 148ad21 and 94e2a36.

📒 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 (6)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Automerge PR autoapproved by a bot
  • GitHub Check: Test NodeJS PR - macos-13
  • GitHub Check: Lighthouse CI
🔇 Additional comments (3)
config/meetings.json (2)

79-85: Approval: New meeting entry "Preventing API Drift: Ensuring Your APIs Stay True to Their Spec".
This new meeting entry has been added with all required fields (calendar link, URL, banner, and ISO8601 date). Please verify that the provided URLs and image asset are correct and that the date is in line with the event’s planned timing.


86-91: Approval: New meeting entry "AsyncAPI Community Working Group Meeting" added.
The new entry appears well formed, with consistent property names and values. Ensure that the scheduled time ("2025-04-08T15:00:00.000Z") is as intended and that it meshes well with the overall meeting schedule in the configuration.

config/newsroom_videos.json (1)

2-7: Approval: New video entry for "AsyncAPI Community Working Group Meeting, March 25th 2025".
The added video entry includes all necessary properties (image_url, title, description, and videoId) and is positioned at the beginning of the array. Please confirm that the details (especially the image URL and video ID) are correct and that the removal of the outdated video entry was intentional.

@asyncapi-bot asyncapi-bot merged commit e160bb5 into master Mar 26, 2025
33 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/148ad215470b33b8868b4bd15d0d59b9bcdb7e52 branch March 26, 2025 00:40
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