chore: add ferror to ambasadors#2099
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
Ferror
changed the title
WalkthroughA new ambassador profile for Zbigniew Malcherczyk was added to Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ 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 |
|
oh nice |
|
I will need to spend some time on providing the things I did, but lets try 😄 |
|
just provide minimum for starter:
|
thulieblack
left a comment
thulieblack
left a comment
There was a problem hiding this comment.
Thanks and welcome to the ambassadors!
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
AMBASSADORS_MEMBERS.yaml (1)
527-535: Addbiofield for consistency with other ambassador entries.This entry is missing the
biofield present in nearly all other ambassador profiles. A short professional summary (1–2 sentences) describing Zbigniew's role or background would maintain schema consistency.Example format (similar to other entries):
bio: "Zbigniew is a Staff Backend Engineer at TransferGo, focusing on event-driven architecture and AsyncAPI adoption."
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
AMBASSADORS_MEMBERS.yaml(1 hunks)
🔇 Additional comments (2)
AMBASSADORS_MEMBERS.yaml (2)
543-548: Verify contribution typecasestudyis valid.Other ambassador entries consistently use type
"article"for case studies (e.g., Ludovic Dussart line 275: "AsyncAPI - Adeo case study" marked asarticle, and Manuel Ottlik line 406: "AsyncAPI - HDI Global SE Case Study" marked asarticle). Confirm whether"casestudy"is a valid/intended type in your schema, or if this should be"article"for consistency.
537-560: Verify PR objectives are met.Per the PR comments from derberg, the following materials were requested:
- PHP conference talk from 2025 (YouTube link) — Not present
- Case study link — ✓ Present (line 543–548)
- Blog post link — ✓ Present (line 537–542)
- Paris 2023 talk (link to slides) — Not clearly present
The contributions include a December 2023 talk with PDF slides and a September 2023 Polish-language talk, but neither is explicitly identified as a Paris 2023 talk. Confirm whether these are sufficient to close the PR objectives or if additional contributions should be added.
| contributions: | ||
| - type: "article" | ||
| title: "How TransferGo adopted AsyncAPI" | ||
| date: | ||
| year: 2025 | ||
| month: "October" | ||
| link: "https://www.asyncapi.com/blog/transfergo-asyncapi-story" | ||
| - type: "casestudy" | ||
| title: "How TransferGo adopted AsyncAPI" | ||
| date: | ||
| year: 2025 | ||
| month: "September" | ||
| link: "https://www.asyncapi.com/casestudies/transfergo" | ||
| - type: "talk" | ||
| title: "Studium przypadku asynchronicznej konsumpcji zdarzeń w domenie finansowej" | ||
| date: | ||
| year: 2023 | ||
| month: "September" | ||
| link: "https://www.youtube.com/watch?v=CtiqwMbOBes" | ||
| - type: "talk" | ||
| title: "How TransferGo uses AsyncAPI to improve Developer Experience" | ||
| date: | ||
| year: 2023 | ||
| month: "December" | ||
| link: "https://github.com/Ferror/keynotes/blob/master/asyncapi-2023-developer-experience.pdf" |
There was a problem hiding this comment.
Fix YAML indentation in contributions list.
The contribution list items are indented with 4 spaces, but should be indented with 6 spaces to match the structure used in other ambassador entries (e.g., Hugo Guerrero at lines 124–137, Ludovic Dussart at lines 225–302).
Apply this diff:
contributions:
- - type: "article"
+ - type: "article"
title: "How TransferGo adopted AsyncAPI"
date:
year: 2025
month: "October"
link: "https://www.asyncapi.com/blog/transfergo-asyncapi-story"
- - type: "casestudy"
+ - type: "casestudy"
title: "How TransferGo adopted AsyncAPI"
date:
year: 2025
month: "September"
link: "https://www.asyncapi.com/casestudies/transfergo"
- - type: "talk"
+ - type: "talk"
title: "Studium przypadku asynchronicznej konsumpcji zdarzeń w domenie finansowej"
date:
year: 2023
month: "September"
link: "https://www.youtube.com/watch?v=CtiqwMbOBes"
- - type: "talk"
+ - type: "talk"
title: "How TransferGo uses AsyncAPI to improve Developer Experience"
date:
year: 2023
month: "December"
link: "https://github.com/Ferror/keynotes/blob/master/asyncapi-2023-developer-experience.pdf"📝 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.
| contributions: | |
| - type: "article" | |
| title: "How TransferGo adopted AsyncAPI" | |
| date: | |
| year: 2025 | |
| month: "October" | |
| link: "https://www.asyncapi.com/blog/transfergo-asyncapi-story" | |
| - type: "casestudy" | |
| title: "How TransferGo adopted AsyncAPI" | |
| date: | |
| year: 2025 | |
| month: "September" | |
| link: "https://www.asyncapi.com/casestudies/transfergo" | |
| - type: "talk" | |
| title: "Studium przypadku asynchronicznej konsumpcji zdarzeń w domenie finansowej" | |
| date: | |
| year: 2023 | |
| month: "September" | |
| link: "https://www.youtube.com/watch?v=CtiqwMbOBes" | |
| - type: "talk" | |
| title: "How TransferGo uses AsyncAPI to improve Developer Experience" | |
| date: | |
| year: 2023 | |
| month: "December" | |
| link: "https://github.com/Ferror/keynotes/blob/master/asyncapi-2023-developer-experience.pdf" | |
| contributions: | |
| - type: "article" | |
| title: "How TransferGo adopted AsyncAPI" | |
| date: | |
| year: 2025 | |
| month: "October" | |
| link: "https://www.asyncapi.com/blog/transfergo-asyncapi-story" | |
| - type: "casestudy" | |
| title: "How TransferGo adopted AsyncAPI" | |
| date: | |
| year: 2025 | |
| month: "September" | |
| link: "https://www.asyncapi.com/casestudies/transfergo" | |
| - type: "talk" | |
| title: "Studium przypadku asynchronicznej konsumpcji zdarzeń w domenie finansowej" | |
| date: | |
| year: 2023 | |
| month: "September" | |
| link: "https://www.youtube.com/watch?v=CtiqwMbOBes" | |
| - type: "talk" | |
| title: "How TransferGo uses AsyncAPI to improve Developer Experience" | |
| date: | |
| year: 2023 | |
| month: "December" | |
| link: "https://github.com/Ferror/keynotes/blob/master/asyncapi-2023-developer-experience.pdf" |
🤖 Prompt for AI Agents
In AMBASSADORS_MEMBERS.yaml around lines 536 to 560, the contributions list
items and their nested fields are indented 4 spaces instead of the expected 6;
update each list item marker and its child keys (type, title, date, year, month,
link) to be indented with 6 spaces to match the other ambassador entries so the
YAML structure aligns consistently.
|
/rtm |
|
@Ferror We invited you to join the AsyncAPI organization, and you are added to the team that lists all Ambassadors. Welcome aboard! We are excited to have you as part of the team. |
4 participants
Lets make this party going 😄
Summary by CodeRabbit