Skip to content

Comments

chore: update meetings.json and newsrooom_videos.json#5188

Merged
asyncapi-bot merged 1 commit intomasterfrom
update-meetings/75cd0ca8485bb6d9945d68c058077b6421c5fc18
Feb 22, 2026
Merged

chore: update meetings.json and newsrooom_videos.json#5188
asyncapi-bot merged 1 commit intomasterfrom
update-meetings/75cd0ca8485bb6d9945d68c058077b6421c5fc18

Conversation

@asyncapi-bot
Copy link
Contributor

@asyncapi-bot asyncapi-bot commented Feb 22, 2026

Automated changes by create-pull-request GitHub action

Summary by CodeRabbit

  • Content Updates
    • Added new videos to the newsroom collection while removing outdated entries.

@netlify
Copy link

netlify bot commented Feb 22, 2026

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 18ff083
🔍 Latest deploy log https://app.netlify.com/projects/asyncapi-website/deploys/699a535ad1df450008fb1e0e
😎 Deploy Preview https://deploy-preview-5188--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 project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 22, 2026

📝 Walkthrough

Walkthrough

This pull request updates the newsroom videos configuration by removing one video entry and adding multiple new video entries to the JSON array, maintaining the consistent object structure with image_url, title, description, and videoId fields.

Changes

Cohort / File(s) Summary
Video Configuration Update
config/newsroom_videos.json
Removed the first video entry and inserted approximately 20 new video objects with standardized metadata (image URLs, titles, descriptions, and video IDs).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

autoapproved, autoupdate

Suggested reviewers

  • derberg
  • akshatnema
  • anshgoyalevil
  • Mayaleeeee
  • princerajpoot20

Poem

🐰 A fresh batch of videos hop in,
Old tales make room for stories to begin,
The newsroom grows with content so fine,
Each frame, each title perfectly aligned,
The rabbit cheers—configuration divine! 📹✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title mentions two files (meetings.json and newsrooom_videos.json) but the commit message indicates three files were updated, including dashboard.json. Additionally, there is a typo: 'newsrooom_videos.json' has three 'o's instead of two. Correct the typo in 'newsrooom_videos.json' to 'newsroom_videos.json' and update the title to include all changed files or use a more accurate summary like 'chore: update configuration files'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch update-meetings/75cd0ca8485bb6d9945d68c058077b6421c5fc18

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud
Copy link

@codecov
Copy link

codecov bot commented Feb 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (75cd0ca) to head (18ff083).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #5188   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           22        22           
  Lines          796       796           
  Branches       146       146           
=========================================
  Hits           796       796           

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@asyncapi-bot
Copy link
Contributor Author

⚡️ Lighthouse report for the changes in this PR:

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

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

@asyncapi-bot asyncapi-bot merged commit 9c6a651 into master Feb 22, 2026
39 of 40 checks passed
@asyncapi-bot asyncapi-bot deleted the update-meetings/75cd0ca8485bb6d9945d68c058077b6421c5fc18 branch February 22, 2026 00:57
@github-project-automation github-project-automation bot moved this from To Be Triaged to Done in Website - Kanban Feb 22, 2026
Copy link
Contributor

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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@config/newsroom_videos.json`:
- Around line 110-127: Two entries share the same "title" ("AsyncAPI Community
WG Meeting , Tuesday July 29th 2025") and "description" URL but different
videoId values (7vvdmDVZPX0 and xD5smwg6az8); either remove the duplicate or
make the titles distinct (e.g., append "Part 1"/"Part 2" or add "(Recording
A/B)") so users can tell them apart—update the objects with videoId 7vvdmDVZPX0
and/or xD5smwg6az8 accordingly.
- Around line 104-109: Fix the typo and extra space in the title field for the
JSON entry with "videoId": "ncOFU__8hLM" by changing the "title" value from
"AsyncAPI Community WG Meeting , Tuesday Auguest 12th 2025" to "AsyncAPI
Community WG Meeting, Tuesday August 12th 2025"; additionally add a
normalization/sanitization step in the generator that trims spaces before
punctuation and applies common typo corrections (e.g., map "Auguest" → "August")
so future titles are auto-fixed at generation time.
- Around line 26-31: The newsroom_videos entry with videoId "yRjdA0DYvBM" (title
"AsyncAPI Community WG Meeting") has an empty "description": "" which will
render blank; update that object's "description" value to a meaningful string
(for example the community issue/meeting URL used by other entries or a short
meeting summary) so the UI shows content instead of an empty slot.

Comment on lines +26 to +31
{
"image_url": "https://i.ytimg.com/vi/yRjdA0DYvBM/hqdefault.jpg",
"title": "AsyncAPI Community WG Meeting",
"description": "",
"videoId": "yRjdA0DYvBM"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Empty description field will render a blank on the newsroom page.

The entry for yRjdA0DYvBM has "description": "". If the UI always renders this field, viewers will see an empty description slot. Consider adding at least the community issue URL (as other meeting entries do) or a short summary once available.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@config/newsroom_videos.json` around lines 26 - 31, The newsroom_videos entry
with videoId "yRjdA0DYvBM" (title "AsyncAPI Community WG Meeting") has an empty
"description": "" which will render blank; update that object's "description"
value to a meaningful string (for example the community issue/meeting URL used
by other entries or a short meeting summary) so the UI shows content instead of
an empty slot.

Comment on lines +104 to +109
{
"image_url": "https://i.ytimg.com/vi/ncOFU__8hLM/hqdefault.jpg",
"title": "AsyncAPI Community WG Meeting , Tuesday Auguest 12th 2025",
"description": "https://github.com/asyncapi/community/issues/2014.",
"videoId": "ncOFU__8hLM"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Typo in title: "Auguest" → "August" (and extra space before comma).

The title on Line 106 reads "AsyncAPI Community WG Meeting , Tuesday Auguest 12th 2025" — two issues:

  • Auguest should be August.
  • There is an extraneous space before the comma, consistent with several other added titles (Lines 94, 112, 118, 124).

If these titles are sourced directly from YouTube metadata, a normalisation/sanitisation step in the generating script would prevent future occurrences.

✏️ Suggested correction
-    "title": "AsyncAPI Community WG Meeting , Tuesday Auguest 12th 2025",
+    "title": "AsyncAPI Community WG Meeting, Tuesday August 12th 2025",
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{
"image_url": "https://i.ytimg.com/vi/ncOFU__8hLM/hqdefault.jpg",
"title": "AsyncAPI Community WG Meeting , Tuesday Auguest 12th 2025",
"description": "https://github.com/asyncapi/community/issues/2014.",
"videoId": "ncOFU__8hLM"
},
{
"image_url": "https://i.ytimg.com/vi/ncOFU__8hLM/hqdefault.jpg",
"title": "AsyncAPI Community WG Meeting, Tuesday August 12th 2025",
"description": "https://github.com/asyncapi/community/issues/2014.",
"videoId": "ncOFU__8hLM"
},
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@config/newsroom_videos.json` around lines 104 - 109, Fix the typo and extra
space in the title field for the JSON entry with "videoId": "ncOFU__8hLM" by
changing the "title" value from "AsyncAPI Community WG Meeting , Tuesday Auguest
12th 2025" to "AsyncAPI Community WG Meeting, Tuesday August 12th 2025";
additionally add a normalization/sanitization step in the generator that trims
spaces before punctuation and applies common typo corrections (e.g., map
"Auguest" → "August") so future titles are auto-fixed at generation time.

Comment on lines +110 to +127
{
"image_url": "https://i.ytimg.com/vi/7vvdmDVZPX0/hqdefault.jpg",
"title": "AsyncAPI Community WG Meeting , Tuesday July 29th 2025",
"description": "https://github.com/asyncapi/community/issues/1988.",
"videoId": "7vvdmDVZPX0"
},
{
"image_url": "https://i.ytimg.com/vi/SaIPQaROWsc/hqdefault.jpg",
"title": "First Meeting of New Governance Board , Tuesday July 29th 2025",
"description": "https://github.com/asyncapi/community/issues/1989.",
"videoId": "SaIPQaROWsc"
},
{
"image_url": "https://i.ytimg.com/vi/xD5smwg6az8/hqdefault.jpg",
"title": "AsyncAPI Community WG Meeting , Tuesday July 29th 2025",
"description": "https://github.com/asyncapi/community/issues/1988.",
"videoId": "xD5smwg6az8"
},
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Two entries with identical title and description for July 29th 2025 — users cannot distinguish them.

Lines 110–115 (videoId: 7vvdmDVZPX0) and Lines 122–127 (videoId: xD5smwg6az8) share the same title and the same description URL. If these are genuinely two separate recordings of the same meeting (e.g., split into parts), their titles should differentiate them (e.g., append "Part 1" / "Part 2"). If one is a duplicate, it should be removed.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@config/newsroom_videos.json` around lines 110 - 127, Two entries share the
same "title" ("AsyncAPI Community WG Meeting , Tuesday July 29th 2025") and
"description" URL but different videoId values (7vvdmDVZPX0 and xD5smwg6az8);
either remove the duplicate or make the titles distinct (e.g., append "Part
1"/"Part 2" or add "(Recording A/B)") so users can tell them apart—update the
objects with videoId 7vvdmDVZPX0 and/or xD5smwg6az8 accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants