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

Merged

Conversation

asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Jan 24, 2025

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Community Updates

    • Removed a Community Meeting scheduled for October 15, 2024
  • Dashboard Changes

    • Updated hot discussions and good first issues
    • Added new discussion about Website Homepage Redesign
    • Added a new issue regarding missing server function
    • Removed outdated issue entries

Copy link
Contributor

coderabbitai bot commented Jan 24, 2025

Walkthrough

This pull request involves updates to two configuration files: config/meetings.json and dashboard.json. In meetings.json, a single Community Meeting entry scheduled for October 15, 2024, was removed. The dashboard.json file underwent more extensive changes, including updates to hot discussions and good first issues, with new entries added, scores modified, and some outdated entries removed.

Changes

File Change Summary
config/meetings.json Removed a Community Meeting entry for October 15, 2024
dashboard.json - Added new discussion: "Website Homepage Redesign"
- Removed discussion about workflow and script checks
- Updated discussion scores
- Added new good first issue: "[BUG] Missing server.title() function"
- Removed issue about terminal help errors

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

🐰 Hop, hop, through config's maze,
Meetings trimmed, dashboard's new phase
Entries dance, some come, some go
In the realm of code's ebb and flow
A rabbit's update, swift and light! 🌟


📜 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 45f6f85 and 76a4501.

📒 Files selected for processing (2)
  • config/meetings.json (0 hunks)
  • dashboard.json (6 hunks)
💤 Files with no reviewable changes (1)
  • config/meetings.json
⏰ Context from checks skipped due to timeout of 180000ms (6)
  • 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: Lighthouse CI
🔇 Additional comments (9)
dashboard.json (9)

12-12: LGTM on score update.
The updated numeric score is valid JSON and there are no apparent issues.


32-32: LGTM on updated score.
All syntax and data structure checks out, with no concerns regarding performance or correctness for this JSON field.


43-43: LGTM on updated score.
No issues detected. This numeric property is properly formatted.


193-206: Entry for “[BUG] Missing server.title() function” looks good.
The syntax is valid JSON. The reference path and metadata seem consistent with how other entries are structured.


207-225: New issue entry for “AsyncAPI Conf 2025 Logo Update.”
All fields look valid and consistent with the existing schema.


226-240: New item to “Improve testing speed by skipping it for certain PRs.”
No issues found. The data structure is aligned with the surrounding JSON.


567-567: Empty labels array.
This change is valid JSON and does not introduce any structural inconsistencies.


178-188: Check the new entry referencing a pull request.
This new entry is associated with PR “ci: add command for transferring issue.” For completeness, verify that the resource path and PR ID match an existing PR in GitHub.

✅ Verification successful

PR reference verification successful
The PR entry in dashboard.json accurately reflects an existing pull request (#314) in the asyncapi/.github repository with matching title and resource path.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Validate the new PR reference.

gh api graphql -f query='
{
  repository(name:".github", owner:"asyncapi") {
    pullRequest(number:314) {
      title
      url
      merged
    }
  }
}'

Length of output: 315


56-71: Verify that the discussion reference is valid.
A new “Website Homepage Redesign” hot discussion has been introduced. If you’d like to confirm that this GitHub issue ID is fully recognized, run the following script.

✅ Verification successful

Discussion reference verified successfully
The GitHub issue #3192 "Website Homepage Redesign" exists in the asyncapi/website repository and is correctly referenced.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the presence of the GitHub issue using the ID from the new entry.
# We'll search references to "Website Homepage Redesign" in the repository, then confirm the ID.

gh api graphql -f query='
{
  repository(name:"website", owner:"asyncapi") {
    issue(number:3192) {
      title
      url
    }
  }
}'

Length of output: 266


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

Copy link

netlify bot commented Jan 24, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 76a4501
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6792e09617d2fc00083d6cc5
😎 Deploy Preview https://deploy-preview-3603--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 Jan 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (45f6f85) to head (76a4501).
Report is 1 commits behind head on master.

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

@asyncapi-bot
Copy link
Contributor Author

⚡️ Lighthouse report for the changes in this PR:

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

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

@asyncapi-bot asyncapi-bot merged commit 1b23c89 into master Jan 24, 2025
33 of 34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/45f6f8566aca6645eb5daa492764754874c796b7 branch January 24, 2025 00:40
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