Skip to content

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented May 30, 2025

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Added two new newsroom video entries, including recent meetings and contributor calls.
  • Chores

    • Removed an outdated meeting entry.
    • Removed two older newsroom video entries to keep content current.

@netlify
Copy link

netlify bot commented May 30, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 0eb30a3
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/6838fdf29e3ae80008d72338
😎 Deploy Preview https://deploy-preview-4139--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 May 30, 2025

Walkthrough

The updates remove the first entry for the "Marketing WG Meeting" dated 2025-02-18 from the meetings configuration file. In the newsroom videos configuration, two new video entries are added at the beginning, and two older entries at the end are removed. No code or exported entities are changed.

Changes

File(s) Change Summary
config/meetings.json Removed the first meeting entry: "Marketing WG Meeting" dated 2025-02-18.
config/newsroom_videos.json Added two new video entries at the start; removed two older video entries at the end.

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

In the warren of config files, I hop,
Old meetings trimmed, new videos atop.
The calendar shifts, the newsroom grows,
With every update, the garden glows.
🥕 A nibble here, a tweak just right,
Content refreshed—what a delight!


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.

@codecov
Copy link

codecov bot commented May 30, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (3a68577) to head (0eb30a3).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #4139   +/-   ##
=========================================
  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 ed22aa2 into master May 30, 2025
32 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/3a68577af03d40d954b7f71eb3ac5d4fa32dc866 branch May 30, 2025 00:42
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 3a68577 and 0eb30a3.

📒 Files selected for processing (2)
  • config/meetings.json (0 hunks)
  • config/newsroom_videos.json (1 hunks)
💤 Files with no reviewable changes (1)
  • config/meetings.json
⏰ Context from checks skipped due to timeout of 180000ms (2)
  • GitHub Check: Automerge PR autoapproved by a bot
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
config/newsroom_videos.json (1)

2-7:

Details

✅ Verification successful

Verify video thumbnail & GitHub issue link availability
Please ensure that the newly added video entry for GSoC Welcome Contributors Call | May 29th 2025 is pointing to valid resources. You can run the following script to confirm both the YouTube thumbnail and the GitHub issue URL return a successful HTTP response:


🏁 Script executed:

#!/bin/bash
# Verify image thumbnail and issue link for videoId 7O85r0YNdvA
urls=(
  "https://i.ytimg.com/vi/7O85r0YNdvA/hqdefault.jpg"
  "https://github.com/asyncapi/community/issues/1922"
)
for url in "${urls[@]}"; do
  if ! curl -sSfI "$url" > /dev/null; then
    echo "❌ Failed to fetch $url"
    exit 1
  fi
done
echo "✅ All links are reachable for videoId 7O85r0YNdvA"

Length of output: 397


✅ Video thumbnail & GitHub issue link are reachable

No further action required.

Comment on lines +8 to +13
{
"image_url": "https://i.ytimg.com/vi/zF5aXQ9A6as/hqdefault.jpg",
"title": "AsyncAPI Design WG Meeting",
"description": "https://github.com/asyncapi/community/issues/1908.",
"videoId": "zF5aXQ9A6as"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Ensure title consistency and verify second entry metadata

  1. The title "AsyncAPI Design WG Meeting" omits the meeting date, whereas other entries embed dates (e.g., comma-separated like “May 20th 2025”). Consider adding the date to match the existing pattern for better uniformity.
  2. Likewise, please verify that the thumbnail and issue link for videoId zF5aXQ9A6as resolve correctly:

🏁 Script executed:

#!/bin/bash
# Verify image thumbnail and issue link for videoId zF5aXQ9A6as
urls=(
  "https://i.ytimg.com/vi/zF5aXQ9A6as/hqdefault.jpg"
  "https://github.com/asyncapi/community/issues/1908"
)
for url in "${urls[@]}"; do
  if ! curl -sSfI "$url" > /dev/null; then
    echo "❌ Failed to fetch $url"
    exit 1
  fi
done
echo "✅ All links are reachable for videoId zF5aXQ9A6as"

Length of output: 397


Add Meeting Date to Title for Consistency
The image thumbnail and issue link for videoId zF5aXQ9A6as have been verified and are reachable.

• In config/newsroom_videos.json (lines 8–13), update the title from

"AsyncAPI Design WG Meeting"

to include the meeting date (for example,

"AsyncAPI Design WG Meeting, May 20th 2025"

) so it matches the date-embedded format used by other entries.

🤖 Prompt for AI Agents
In config/newsroom_videos.json around lines 8 to 13, update the title field by
appending the meeting date to "AsyncAPI Design WG Meeting" so it matches the
date-embedded format of other entries, for example changing it to "AsyncAPI
Design WG Meeting, May 20th 2025". This ensures consistency in title formatting
across all entries.

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