chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• Updates
  • Updated discussion scores for multiple entries in hot discussions
  • Added a new discussion about "Website Homepage Redesign" with a bounty label
  • Replaced an existing discussion entry with a new one

[coderabbitai]

Walkthrough

The pull request involves updates to the dashboard.json file, focusing on the hotDiscussions section. The changes include score modifications for three existing discussions and the addition of a new discussion entry about the Website Homepage Redesign. An entry with the same ID was simultaneously removed, suggesting a dynamic update to the discussions tracking mechanism.

Changes

File	Change Summary
dashboard.json	- Updated scores for 3 discussions in hotDiscussions - Added new discussion entry for Website Homepage Redesign - Removed previous entry with same ID

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3580: Modifies dashboard.json, specifically updating the hotDiscussions section

Suggested labels

autoapproved, autoupdate

Poem

🐰 Hop, hop, through the dashboard's maze,
Discussions dance, their scores ablaze!
New entries bounce, old ones take flight,
A rabbit's view of data's delight!
JSON magic, ever so bright! 🌟

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between eb13e0b and 2493292.

📒 Files selected for processing (1)

• dashboard.json (5 hunks)

⏰ Context from checks skipped due to timeout of 180000ms (3)

• GitHub Check: Automerge PR autoapproved by a bot
• GitHub Check: Test NodeJS PR - macos-13
• GitHub Check: Lighthouse CI

🔇 Additional comments (4)

dashboard.json (4)

12-12: Score updates look consistent.

The score updates for the discussions maintain proper numerical precision and follow the existing pattern.

Also applies to: 32-32, 43-43

---

92-107: New discussion entry is properly structured.

The Website Homepage Redesign entry follows the correct format with all required fields:

• Proper ID format
• Boolean flags for PR and assignment status
• Complete metadata (title, author, path, repo)
• Valid label structure
• Consistent score format

---

159-174: New discussion entry is properly structured.

The AACoT'24 Conference Website Gallery entry follows the correct format with all required fields:

• Proper ID format
• Boolean flags for PR and assignment status
• Complete metadata (title, author, path, repo)
• Valid label structure with Hacktoberfest tag
• Consistent score format

---

Line range hint 1-674: Verify JSON structure integrity.

The overall JSON structure maintains proper nesting and array consistency.

✅ Verification successful

JSON structure verified successfully

• All required fields are present and properly formatted
• No syntax errors or missing data detected

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify JSON syntax and structure
cat dashboard.json | jq '.' > /dev/null
if [ $? -eq 0 ]; then
    echo "JSON syntax is valid"
else
    echo "JSON syntax error detected"
fi

# Verify all required fields are present in hot discussions
jq '.hotDiscussions[] | select(.id == null or .isPR == null or .isAssigned == null or .title == null or .author == null or .resourcePath == null or .repo == null or .labels == null or .score == null)' dashboard.json

Length of output: 314

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	2493292
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/678af74da8dec10008a8d83b
😎 Deploy Preview	https://deploy-preview-3584--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 (eb13e0b) to head (2493292).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3584   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           19        19           
  Lines          668       668           
=========================================
  Hits           668       668           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	35
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-3584--asyncapi-website.netlify.app/