chore(blog): board nomination for 2026#5239
chore(blog): board nomination for 2026#5239thulieblack wants to merge 10 commits intoasyncapi:masterfrom
Conversation
✅ Deploy Preview for asyncapi-website ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughRemoved the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
@thulieblack you may want to mention that we're electing 3 members this year instead of the planned 2 because I'm stepping down. |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-5239--asyncapi-website.netlify.app/ |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5239 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 830 830
Branches 159 159
=========================================
Hits 830 830 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@markdown/blog/board-nomination.md`:
- Around line 53-63: Standardize the timeline wording and timestamps: update the
sentence "Nominations are open from the **1st to the 26th of April at 12.00 PM
UTC**" to a consistent format with explicit year and time zone (e.g.,
"Nominations are open from 1 April 2026 until 26 April 2026 at 12:00 PM UTC"),
ensure the summary list entries match that same style (use "1 April 2026" not "1
of April 2026", and "26 April 2026" with the same time format where applicable),
and add the missing year to the standalone sentence "Candidates will be
announced on 30 April." so all dates consistently include the year and use the
same time format (e.g., "12:00 PM UTC").
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 1ce19a74-664a-4ece-aa26-db154a0802ca
📒 Files selected for processing (4)
markdown/blog/2026-february-summary.mdmarkdown/blog/board-nomination.mdmarkdown/blog/release-notes-3.1.0.mdpublic/img/posts/2026-blog-banner/nominations.webp
💤 Files with no reviewable changes (2)
- markdown/blog/release-notes-3.1.0.md
- markdown/blog/2026-february-summary.md
63c3f64
|
@TRohit20 please your approval |
|



Board Nominations for 2026
Summary by CodeRabbit