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

Merged

Conversation

asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Nov 26, 2024

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • New Features

    • Introduced a new issue titled "Return to top arrow feature/button" in the good first issues section.
    • Added two new discussions in the hot discussions section.
  • Updates

    • Updated scores for existing discussions to reflect their new rankings.
    • Modified assignment status for an existing issue to indicate it is now assigned.
    • Updated labels for some issues, including the addition of a "stale" label.
  • Bug Fixes

    • Removed outdated discussions and issues to streamline content.

Copy link

coderabbitai bot commented Nov 26, 2024

Walkthrough

The changes in this pull request involve modifications to the dashboard.json file, specifically within the hotDiscussions and goodFirstIssues sections. Adjustments include the removal and addition of entries, updates to discussion scores, changes in issue assignment statuses, and label modifications. Notably, one discussion's score increased, while another was reintroduced. The goodFirstIssues section also saw the addition of a new issue and updates to existing issues' statuses and labels.

Changes

File Change Summary
dashboard.json - Removed one entry from hotDiscussions.
- Added two new entries to hotDiscussions.
- Updated score for one discussion (22.11 to 27.86) and another (21.54 to 21.83).
- Reintroduced discussion with score 16.61.
- Added new issue "Return to top arrow feature/button" in goodFirstIssues.
- Changed isAssigned status from false to true for an existing issue.
- Removed one entry from goodFirstIssues.
- Updated labels for some issues, adding a "stale" label.

Possibly related PRs

Suggested reviewers

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

🐰 In the garden where ideas bloom,
Hot discussions spark, dispelling gloom.
Good first issues, fresh and bright,
With labels added, they take flight.
A rabbit hops, with joy and cheer,
Celebrating changes, oh so dear! 🌼


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between bff75f4 and 48d8423.

📒 Files selected for processing (1)
  • dashboard.json (9 hunks)
🔇 Additional comments (7)
dashboard.json (7)

41-42: LGTM: Score updates reflect current engagement metrics.

The score updates across multiple discussions accurately reflect the current engagement metrics and maintain proper numerical formatting.

Also applies to: 95-95, 180-180, 191-191


43-52: LGTM: New PR entry is well-structured.

The new PR entry for "feat: add tests for build post list script" is properly formatted and includes all required fields.


119-138: LGTM: Community cards implementation entry is properly structured.

The entry for "Community cards implementation" is well-formatted with appropriate labels and scoring.


195-209: LGTM: New good first issue is properly formatted.

The new good first issue "Return to top arrow feature/button" is well-structured with appropriate labels and metadata.


228-228: LGTM: Assignment status update is correct.

The assignment status change for the mentees design issue is properly reflected.


739-742: LGTM: Stale label addition is appropriate.

The addition of the "stale" label to the technical writers' onboarding guide issue follows the repository's maintenance practices.


155-170: Verify the educational video entry's status.

The entry for "Create educational & technical video explaining AsyncAPI's main features" has been reintroduced. Let's verify if this is intentional and if there are any dependencies or related tasks.

✅ Verification successful

The educational video issue is still open and actively tracked

The issue (#155) for creating educational & technical video is currently in an OPEN state, confirming that its presence in the dashboard is intentional and valid. The task appears to be part of broader educational initiatives, as evidenced by its mention in ambassador responsibilities.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for related issues or PRs about the educational video
# Test: Search for related discussions or PRs about the educational video feature

# Search for related issues
rg -i "educational.*video|technical.*video" 

# Search for related PRs
gh api graphql -f query='
{
  search(query: "repo:asyncapi/community educational video technical video", type: ISSUE, first: 5) {
    nodes {
      ... on Issue {
        title
        state
        url
      }
    }
  }
}'

Length of output: 809


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.

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 Nov 26, 2024

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 48d8423
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/6745189e39454a00082629a4
😎 Deploy Preview https://deploy-preview-3430--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 Nov 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.77%. Comparing base (914ab3b) to head (48d8423).
Report is 2 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3430   +/-   ##
=======================================
  Coverage   67.77%   67.77%           
=======================================
  Files          21       21           
  Lines         664      664           
=======================================
  Hits          450      450           
  Misses        214      214           

☔ 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-3430--asyncapi-website.netlify.app/

@asyncapi-bot asyncapi-bot merged commit 7669160 into master Nov 26, 2024
34 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/bff75f4fee4da37a388fa6ca68876dff60431a64 branch November 26, 2024 00:44
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