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

Merged

Conversation

asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Oct 29, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Added a new video entry for the "AsyncAPI Conference Dry Run" in the newsroom.
    • Introduced a new pull request regarding the CSS alignment of the calendar component on the home page.
  • Updates

    • Adjusted scores for various discussions and pull requests on the dashboard to reflect recent activity.
    • Removed an outdated pull request related to the Bounty Program Rules.

Copy link

coderabbitai bot commented Oct 29, 2024

Walkthrough

The changes involve updates to two JSON configuration files: newsroom_videos.json and dashboard.json. In newsroom_videos.json, a new video entry for the "AsyncAPI Conference Dry Run" is added, replacing an existing entry for the "Design Onboarding Call." The dashboard.json file sees several score adjustments for existing discussions and the addition of a new pull request, while an old pull request is removed.

Changes

File Change Summary
config/newsroom_videos.json - Added a new video entry for "AsyncAPI Conference Dry Run" with fields: image_url, title, description, videoId.
- Removed the entry for "Design Onboarding Call" with similar fields.
dashboard.json - Updated scores for various discussions and pull requests.
- Added a new pull request titled "fix: css alignment of calendar component on the home page" with a score of approximately 11.20.
- Removed the pull request titled "docs: add Bounty Program Rules."

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

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

Poem

In the JSON fields, a change we see,
A new video entry, hopping with glee.
Scores updated, some rise, some fall,
A dashboard refreshed, it welcomes us all.
With each little tweak, our project takes flight,
Hooray for the changes, everything feels right! 🐇✨


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

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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 Oct 29, 2024

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 6e97924
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67202e56f05ae900080a4f1d
😎 Deploy Preview https://deploy-preview-3341--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

@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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7753444 and 6e97924.

📒 Files selected for processing (2)
  • config/newsroom_videos.json (1 hunks)
  • dashboard.json (6 hunks)
🔇 Additional comments (3)
dashboard.json (3)

39-39: Score updates look consistent.

The score increments (~0.287) appear systematic across all updated entries, maintaining the relative ranking order.

Also applies to: 50-50, 70-70, 81-81, 92-92


132-142: New PR entry is properly structured.

The new pull request entry maintains consistent formatting and is correctly positioned based on its score value.


Line range hint 1-600: Overall structure maintains consistency.

The JSON structure remains valid with proper ordering of entries by score, and all entries follow the consistent schema pattern.

Comment on lines +2 to +7
{
"image_url": "https://i.ytimg.com/vi/Hy3-C6V2ir8/hqdefault.jpg",
"title": "AsyncAPI Conference Dry Run",
"description": "Setup and conference prep.",
"videoId": "Hy3-C6V2ir8"
},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codebase verification

Update the video entry format to match the established pattern

Based on the meetings.json and newsroom_videos.json content, the Conference Dry Run entry should be updated to:

All other video entries follow this consistent format with date, time, and GitHub issue reference. The corresponding meeting entry in meetings.json confirms these details.

🔗 Analysis chain

Verify the description format consistency.

While the JSON structure is valid and the video references are correct, the description format differs from other entries in the file. Other entries typically include:

  • Date and time information
  • A GitHub issue reference

Consider updating the description to match the established pattern if this is a recorded meeting.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check if there's a corresponding GitHub issue for this video
# that should be referenced in the description

# Search for any issues mentioning the Conference Dry Run
rg -i "conference.*dry.*run" --glob "*.{md,json}"

Length of output: 256


Script:

#!/bin/bash
# Let's check the content of meetings.json to see if we can find more context
cat config/meetings.json

Length of output: 7932


Script:

#!/bin/bash
# Let's check the format of other entries in newsroom_videos.json for comparison
cat config/newsroom_videos.json

Length of output: 1255

@asyncapi-bot
Copy link
Contributor Author

⚡️ Lighthouse report for the changes in this PR:

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

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

@asyncapi-bot asyncapi-bot merged commit 85c9a35 into master Oct 29, 2024
32 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/7753444299abdb99797fe6097a5683b0d6c13f2a branch October 29, 2024 00:41
Copy link

codecov bot commented Oct 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 49.14%. Comparing base (7753444) to head (6e97924).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3341   +/-   ##
=======================================
  Coverage   49.14%   49.14%           
=======================================
  Files          21       21           
  Lines         647      647           
=======================================
  Hits          318      318           
  Misses        329      329           

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

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