chore: update meetings.json and newsrooom_videos.json

[asyncapi-bot]

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

• New Features

  • Introduced a new community discussion titled "Budget 2025" featuring multiple enhancements.
  • Added fresh contribution opportunities, including options for social sharing on blogs and smoother search modal transitions.

• Chores

  • Updated display metrics and refined labels for discussions and contribution items.
  • Replaced and removed outdated issues to ensure the most current content is presented.

[coderabbitai]

Walkthrough

This pull request updates the dashboard.json file. In the hotDiscussions section, it increases the score of an existing discussion and adds a new "Budget 2025" discussion with multiple labels. In the goodFirstIssues section, it replaces a previous issue, adds two new issues with updated resource paths, authors, and labels, and removes outdated entries. The changes also include modifications to label values.

Changes

File

Changes

dashboard.json

hotDiscussions: Updated score for "refactor: migrate build script to typescript"; added new discussion "Budget 2025" with labels enhancement, vote, gitvote, and vote open. goodFirstIssues: Replaced the "[Bug]: The Search History from Search Bar and Search Icon is not consistent" issue; added "[FEATURE] " and "[FEATURE] Add smooth transition to the search modal opening" issues; removed outdated entries and updated labels.

Possibly related PRs

• chore: update meetings.json and newsrooom_videos.json #3329: Updates to the hotDiscussions section, including score adjustments and new entries, align closely with these changes.
• chore: update meetings.json and newsrooom_videos.json #3438: Modifies both the hotDiscussions and goodFirstIssues sections, mirroring the update patterns in this PR.
• chore: update meetings.json and newsrooom_videos.json #3580: Involves similar modifications in dashboard.json with updated scores and new issue additions.

Suggested labels

autoapproved, autoupdate

Suggested reviewers

• derberg
• akshatnema
• magicmatatjahu
• devilkiller-ag
• sambhavgupta0705
• anshgoyalevil
• Mayaleeeee

Poem

Hopping through lines of JSON neat,
I adjust scores with nimble feet,
New discussions bloom, fresh and bright,
Bugs and issues take their flight.
In this code garden, I joyfully repeat,
A rabbit’s dance to make updates complete!
(_/) 🥕

---

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	7de5ebf
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67b3d64ca3f3800008a78978
😎 Deploy Preview	https://deploy-preview-3702--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 (1b240da) to head (7de5ebf).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #3702   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           20        20           
  Lines          732       732           
=========================================
  Hits           732       732           

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

dashboard.json (3)

168-177: New GoodFirstIssue: Octokit Package Update
A new issue entry for updating support to @octokit/request v9 and @octokit/graphql v8 has been added. The fields (id, resourcePath, repo, author, area, and labels) seem to be correctly populated. Consider adding a bit more context or pointers in the issue description for new contributors if needed.

---

203-217: New GoodFirstIssue: Smooth Transition for Search Modal
The addition of the issue "[FEATURE] Add smooth transition to the search modal opening" is noted. One point to verify is that the area is set as "Unknown"—confirm if this is intended or if it should be updated for better categorization.

---

218-232: New GoodFirstIssue: Scroll-to-Top Button Design Improvement
The issue "[FEATURE] Improving scroll to top button elegent and clean design" has been introduced. The implementation is correct; however, please confirm whether "elegent" is an intentional choice or a typographical error (likely intended to be "elegant").

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 1b240da and 7de5ebf.

📒 Files selected for processing (1)

• dashboard.json (3 hunks)

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

• 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 - windows-latest
• GitHub Check: Test NodeJS PR - macos-13
• GitHub Check: Lighthouse CI

🔇 Additional comments (4)

dashboard.json (4)

12-12: Score Update for Existing Discussion
The score for the discussion titled "refactor: migrate build script to typescript" has been updated to 62.31688575858915. This update appears consistent with the expected metric improvements.

---

116-143: New Discussion Entry: "Budget 2025"
A new discussion item for "Budget 2025" has been added with all the required fields including proper labels (enhancement, vote, gitvote, vote open) and a score of 14.358729437462937. Please verify that the score and label color codes align with the overall dashboard strategy.

---

178-187: Replaced Bug Issue: Search History Inconsistency
The issue titled "[Bug]: The Search History from Search Bar and Search Icon is not consistent" has been updated with a new resource path and author information. Ensure that this change correctly reflects the latest reported issue and that any downstream references to the old issue are updated accordingly.

---

188-202: New GoodFirstIssue: Social Sharing Buttons Feature
A new issue entry "[FEATURE] " targeting social sharing functionality has been added under the typescript area with an "enhancement" label. This looks well formatted. Ensure that the issue description provides enough technical context for contributors.