chore: add @Adi-204 to TSC as maintainer of generator

[Adi-204]

Description
Add @Adi-204 to TSC as maintainer of generator after merge of asyncapi/generator#1685

Summary by CodeRabbit

• Documentation
  • Updated maintainer profile details and availability information.
• Chores
  • Added maintainer contact and social links.
  • Updated maintainer team membership status.

No user-facing changes or functionality impacts.

[coderabbitai]

Walkthrough

Updated MAINTAINERS.yaml for Adi Boghawala: set isTscMember to true and added linkedin, slack, and availableForHire fields. No other files or logic changed.

Changes

Cohort / File(s)	Summary
Maintainers metadata MAINTAINERS.yaml	Modified Adi Boghawala entry: isTscMember set to true; added fields: linkedin (adi-boghawala), slack (U0867GV384D), availableForHire (true). Existing twitter retained; other fields unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs(maintainers): update MAINTAINERS.yaml file with the latest CODEOWNERS changes #2045 — Also updates the Adi Boghawala block in MAINTAINERS.yaml (github/twitter restructuring), overlapping the same entry.
• docs(community): update latest maintainers list #2044 — Introduces/adjusts the Adi Boghawala maintainer entry, related to the same section being updated here.

Suggested reviewers

• derberg
• bandantonio
• thulieblack
• asyncapi-bot-eve

Poem

A nibble of YAML beneath moonlight’s glow,
I hop through fields where maintainer tags grow.
A twitch of the whiskers, a flag flipped to true—
LinkedIn and Slack, now part of the view.
Carrots for hiring? I’ll bring a few. 🥕🐇

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[github-actions]

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.

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

MAINTAINERS.yaml (1)

755-765: Fix CI: Move “Adi Boghawala” entry to the A-section (alphabetical order).

The list appears alphabetized by name; adding Adi at the bottom breaks the validators. Please relocate the entire block to the correct A-position (near other “A…” names). This is the most likely cause of the Ajv validation failure reported by the workflow.

Apply this minimal removal here, then re-insert the same block in the correct alphabetical spot above:

- - name: Adi Boghawala
-   github: Adi-204
-   twitter: AdiBoghawala
-   linkedin: adi-boghawala
-   slack: U0867GV384D
-   availableForHire: true
-   isTscMember: true
-   repos:
-     - generator
-   githubID: 114283933

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4d7ac62 and 96d2c3d.

📒 Files selected for processing (1)

• MAINTAINERS.yaml (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Validating the list of maintainers

MAINTAINERS.yaml

[error] 1-1: GitHub Action step 'actions/github-script@v4' failed: MAINTAINERS.yaml did not conform to the validation schema (Ajv).

[derberg]

Happy to welcome you @Adi-204 👏🏼

[derberg]

/rtm