chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Added a new dashboard entry for the upcoming AsyncAPI Meetups Page on the conference website, now reflecting designated assignment details.

• Chores

  • Updated prioritization metrics and replaced an outdated entry to ensure the dashboard displays current and accurate information.

[coderabbitai]

Walkthrough

This pull request updates the dashboard.json file by recalculating scores for two issues and replacing an existing issue with a new one. The modifications involve updating the numeric scores for issue IDs PR_kwDODCuNRs6NwyqP and I_kwDOFLhIt86O7jFN and substituting issue I_kwDODyzcIc5gD3jB with entry I_kwDODwv8N86un74M that includes new attributes such as title, author, and resource path.

Changes

File

Change Summary

dashboard.json

- Updated score for issue PR_kwDODCuNRs6NwyqP from 32.16355393991698 to 32.45072852866624. - Updated score for issue I_kwDOFLhIt86O7jFN from 18.953522857451077 to 19.240697446200336. - Replaced issue I_kwDODyzcIc5gD3jB with new issue I_kwDODwv8N86un74M (isPR: false, isAssigned: true, title: "Add AsyncAPI Meetups Page to Conference Website", author: "Shriya-Chauhan", resourcePath: "/asyncapi/conference-website/issues/644", repo: "asyncapi/conference-website", score: 13.78438025996442, no labels).

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3935: Modifies the dashboard.json file in a related manner by adding new entries and restructuring existing ones.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

I hopped through JSON in the midnight hue,
Scores and issues danced to something new.
Two values climbed to brighter heights,
One old entry vanished from our sights.
A fresh meet-up issue now shines in view –
Code and carrots, a change so true!
🐇💻✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	04747d5
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67f07bac2613e0000839297a
😎 Deploy Preview	https://deploy-preview-4017--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle 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]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c06761e) to head (04747d5).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #4017   +/-   ##
=========================================
  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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

dashboard.json (2)

23-23: Score Update for PR_kwDODCuNRs6NwyqP
The score for issue "PR_kwDODCuNRs6NwyqP" has been updated to 32.45072852866624. Please confirm that the recalculated value is derived correctly from the intended metrics.

---

95-95: Score Update for I_kwDOFLhIt86O7jFN
The score for issue "I_kwDOFLhIt86O7jFN" is now 19.240697446200336. Verify that this update aligns with the latest recalculation rules and accurately reflects the desired adjustments.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between c06761e and 04747d5.

📒 Files selected for processing (1)

• dashboard.json (3 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 (2)

dashboard.json (2)

178-186: Addition of New Issue Object
A new issue with ID "I_kwDODwv8N86un74M" has been added with complete and well-structured attributes (including isPR, isAssigned, title, author, resourcePath, repo, labels, and score). Please ensure that the old issue (previously with ID "I_kwDODyzcIc5gD3jB") has been removed as intended and that this replacement is reflected consistently across the system.

---

1-1: Note on File Scope vs. PR Objectives
The pull request description mentions updates to meetings.json and newsrooom_videos.json, yet the current file under review is dashboard.json. Please confirm that this file update fits within the intended scope of the PR.