chore(blog): add-gravitee-sponsorship-2025#4257
chore(blog): add-gravitee-sponsorship-2025#4257iambami wants to merge 22 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. |
WalkthroughA new markdown blog post was added announcing Gravitee's renewed platinum sponsorship of the AsyncAPI community for 2025. The article details Gravitee’s involvement, the partnership's goals, and its impact on the AsyncAPI ecosystem, including support for events, tooling, and community initiatives. Changes
Suggested labels
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
Documentation and Community
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4257 +/- ##
=========================================
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: 0
🧹 Nitpick comments (4)
markdown/blog/gravitee-sponsorship-2025.md (4)
35-38: Pluralize “cost” and split the long bullet for readabilityMinor copy tweaks:
- “cost” ➔ “costs”
- The fourth bullet is ~200 chars and hard to scan inside a list. Consider turning it into a follow-up paragraph after the list.
- - Operational and travel cost for events + - Operational and travel costs for events ... - - When we say Gravitee is helping us “hold nothing back,” we mean it, they’re helping build an ecosystem where everyone can contribute, learn, and grow, no matter their location or technical background.
44-49: Fix list nesting – header bullet renders oddlyRight now “By adopting AsyncAPI, Gravitee:” shows as a regular list item followed by peer items. For proper Markdown semantics:
- - By adopting AsyncAPI, Gravitee: - - Enables better **discoverability** … - - Enforces consistent **governance** … - - Improves **observability** … - - Reduces the **complexity** … +**By adopting AsyncAPI, Gravitee …** + + - Enables better **discoverability** … + - Enforces consistent **governance** … + - Improves **observability** … + - Reduces the **complexity** …This renders as a heading-style intro plus an indented sub-list, avoiding the current flat bullet soup.
56-63: Promote “Stay Connected” to a heading and tighten layoutHelps scanners reach the CTA section quickly.
-💜 Thank you, Gravitee, for standing with us, and for continuing to believe in the power of open, asynchronous systems. -Stay Connected +💜 Thank you, Gravitee, for standing with us, and for continuing to believe in the power of open, asynchronous systems. + +### Stay ConnectedAlso consider putting the external links in a bullet list under a single “Follow Gravitee” bullet to reduce visual noise.
64-64: Remove duplicate “more”-Stay tuned for more updates as we get closer to more AsyncAPI Conference 2025! +Stay tuned for updates as we get closer to AsyncAPI Conference 2025!
📜 Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
markdown/blog/gravitee-sponsorship-2025.md(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: asyncapi-bot
PR: asyncapi/website#0
File: :0-0
Timestamp: 2025-02-18T12:07:42.211Z
Learning: The following PR commands are supported in the asyncapi/website repository:
- `/please-take-a-look` or `/ptal`: Requests attention from reviewers who haven't reviewed the PR
- `/ready-to-merge` or `/rtm`: Triggers automerge when all conditions are met
- `/do-not-merge` or `/dnm`: Blocks automerge even if all conditions are met
- `/autoupdate` or `/au`: Adds autoupdate label to keep PR in sync with target branch
- `/update` or `/u`: One-time update of PR with latest changes from target branch
markdown/blog/gravitee-sponsorship-2025.md (1)
Learnt from: iambami
PR: asyncapi/website#4111
File: markdown/blog/community-spotlight-aayush.md:3-3
Timestamp: 2025-06-03T06:48:09.304Z
Learning: For AsyncAPI community spotlight blog posts, the frontmatter date should reflect the actual publication date, not the month being highlighted in the spotlight. For example, a "May Community Spotlight" can be published in June with a June date in the frontmatter.
⏰ Context from checks skipped due to timeout of 180000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Lighthouse CI
🔇 Additional comments (1)
markdown/blog/gravitee-sponsorship-2025.md (1)
3-4: Double-check front-matter conventions
- Is the
dateset to the intended publication day?- Some past posts use
type: communication(lowercase). Verify with the site’s front-matter schema to avoid build-time validation errors.
|
Thank you all for your feedback. I will implement them. |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-4257--asyncapi-website.netlify.app/ |
|
Changes made folks. |
|
The recent update has been done. Can you give this another review? |
|
#4257 (comment) @iambami please address these changes first |
|
@princerajpoot20 please approve and get this merged |
|
/rtm |
|
@princerajpoot20 the Cypress test are failing. thats why its not being able to be merged |
|
@thulieblack I don't think so that is the reason, Cypress test is not marked as mandatory in CI/CD. those are optional |
|
|
@bandantonio your approval please, since you requested changes |
|
We had Gravitee return as our platinum sponsor this year, and here is the announcement blog.
Ready for review @derberg @thulieblack @TRohit20 @akshatnema
Summary by CodeRabbit