Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update meetings.json and newsrooom_videos.json #3873

Merged

Conversation

asyncapi-bot
Copy link
Contributor

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

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Added a new event for the AsyncAPI Community Working Group Meeting with complete details.
    • Updated video listings by introducing a new meeting video and refreshing existing content with updated event information.
    • Enhanced dashboard displays with refined issue and discussion listings.
  • Bug Fixes

    • Resolved a file-generation issue to ensure the proper JSON output is generated instead of YAML.

Copy link
Contributor

coderabbitai bot commented Mar 12, 2025

Walkthrough

This pull request updates several JSON configuration files. A new meeting entry for the AsyncAPI Community Working Group Meeting on March 25, 2025, is added to config/meetings.json. In config/newsroom_videos.json, a new video entry for a March 11th, 2025 meeting is introduced and an existing video entry is replaced with updated event details. The dashboard.json file sees modifications including score adjustments, removal of an outdated proposal, addition of a new bug report entry, and changes to issue entry details.

Changes

File(s) Change Summary
config/meetings.json, config/newsroom_videos.json Added new event entries: a new meeting entry (AsyncAPI Community Working Group Meeting on Mar 25, 2025) with full details in meetings.json, and in newsroom_videos.json a new video entry for Mar 11, 2025 plus replacement of an existing video entry.
dashboard.json Updated dashboard configurations: score modifications, removal of a proposal entry, addition of a new bug-report entry, and alterations in issue details including type and title changes.

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

Oh, I’m a rabbit with a joyful hop,
Leaping over JSON fields that never stop.
New meetings and videos neatly in a row,
Dashboard fixes making our progress glow.
Carrots and commits in a garden of code,
Celebrating changes on our bright new road.
🥕✨ Happy updates in every byte mode!


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

netlify bot commented Mar 12, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 4881f09
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67d0d78e8e81b300080f0ed1
😎 Deploy Preview https://deploy-preview-3873--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.

Copy link

codecov bot commented Mar 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (b02e479) to head (4881f09).
Report is 1 commits behind head on master.

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

@asyncapi-bot asyncapi-bot merged commit 74d716f into master Mar 12, 2025
32 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/b02e479c6aed5785cb696379f183b76b496bf2c3 branch March 12, 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: 0

🧹 Nitpick comments (1)
dashboard.json (1)

162-176: Verify Existence of Proposal Entry

The entry "Proposal to add a 'version' value into the message object to support a more granular versioning" appears in the hotDiscussions list. However, the PR objectives mention the removal of an outdated proposal. Please review and confirm whether this entry should remain or be removed.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b02e479 and 4881f09.

📒 Files selected for processing (3)
  • config/meetings.json (1 hunks)
  • config/newsroom_videos.json (2 hunks)
  • dashboard.json (2 hunks)
⏰ Context from checks skipped due to timeout of 180000ms (5)
  • 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: Lighthouse CI
🔇 Additional comments (7)
config/meetings.json (1)

71-78: New Meeting Entry Added as Expected

The newly added "AsyncAPI Community Working Group Meeting" entry for March 25, 2025 is well-formed with all required fields (title, calLink, url, banner, date). Please double-check that the calendar link and GitHub issue URL are correct and align with the intended event.

config/newsroom_videos.json (2)

2-7: New Video Entry Addition

The new video entry "AsyncAPI Community Working Group Meeting, March 11th 2025" has been added with the appropriate image URL, title, description, and videoId. Ensure the description URL ("asyncapi/community#1754.") accurately reflects the issue reference.


27-30: Updated Video Entry Replacement

The existing video entry has been replaced with updated details for "Event-Driven and OpenTelemetry with Eduardo". The new image URL, title, description, and videoId appear correct. Please confirm these changes reflect the intended event update.

dashboard.json (4)

80-89: Updated Score for Blog Spotlight Entry

The score for the "chore(blog): add ashmit spotlight story" entry has been updated to 14.645904026212197. Please verify that this updated metric accurately reflects the latest community engagement data.


146-160: Converted PR to Issue for Website Redesign

The entry "Redesign the AsyncAPI Website and Implement Dark Theme" now features an updated ID, is marked as an issue (with "isPR": false), and includes new label details. Confirm that these changes correctly represent the current discussion status.


177-200: Donation Entry Updated

The "Donation of Neuroglia.AsyncAPI" entry now includes updated vote labels and score. Verify that these updates accurately reflect the current data and that the vote-related details are correct.


203-217: New Good-First-Issue Entry Added

A new bug report entry has been added detailing an issue where a YAML file is generated instead of a JSON file when using the asyncapi new file command. The provided metadata (including the resource path /asyncapi/cli/issues/1710) appears accurate—please confirm that all details match the observed behavior.

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.

2 participants