Skip to content

chore: add @Adi-204 to CODEOWNERS as templates champion that joins maintainers list#1685

Merged
asyncapi-bot merged 4 commits intoasyncapi:masterfrom
derberg:adimaintainer
Aug 26, 2025
Merged

chore: add @Adi-204 to CODEOWNERS as templates champion that joins maintainers list#1685
asyncapi-bot merged 4 commits intoasyncapi:masterfrom
derberg:adimaintainer

Conversation

@derberg
Copy link
Member

@derberg derberg commented Aug 25, 2025

@Adi-204 proved over the last couple of months that he deserves the trust to join the project and share its responsibility. He's the main driver of the change that takes place in the repo, related to templates development and is alrady in the position to accept and merge related PRs. He acted as triager of issues and PRs over the last few months like a pro!

Summary by CodeRabbit

  • Chores
    • Updated repository ownership rules to clarify reviewers and responsibilities.
    • Defined core maintainers: @derberg, @magicmatatjahu, @jonaslagoni, @asyncapi-bot-eve.
    • Assigned package-area ownership to @Adi-204 (Templates Champion).
    • Assigned documentation ownership to @Florence-Njeri (Docs Champion), @derberg, and @asyncapi-bot-eve.
    • Set changeset docs ownership to core maintainers to avoid notifying Docs Champions.
    • Improves review routing and accountability without affecting application behavior.

@changeset-bot
Copy link

changeset-bot bot commented Aug 25, 2025

⚠️ No Changeset found

Latest commit: eccacda

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link

coderabbitai bot commented Aug 25, 2025

Walkthrough

Added a CODEOWNERS file with core maintainers, ownership for the packages/ directory, and ownership rules for Markdown files and changeset markdowns. No source code or behavior changes.

Changes

Cohort / File(s) Summary of Changes
Repository metadata
CODEOWNERS
Added core maintainers: @derberg, @magicmatatjahu, @jonaslagoni, @asyncapi-bot-eve; added packages/ ownership assigned to @Adi-204 (Templates Champion); added *.md ownership assigned to @Florence-Njeri, @derberg, @asyncapi-bot-eve (Docs Champion).
Changeset overrides
.changeset/**/*.md
Added override so changeset markdown files are owned by @derberg, @magicmatatjahu, @asyncapi-bot-eve (Docs Champions excluded).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • 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.

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.

@asyncapi-bot
Copy link
Contributor

What reviewer looks at during PR review

The following are ideal points maintainers look for during review. Reviewing these points yourself beforehand can help streamline the review process and reduce time to merge.

  1. PR Title: Use a concise title that follows our Conventional Commits guidelines and clearly summarizes the change using imperative mood (it means spoken or written as if giving a command or instruction, like "add new helper for listing operations")

    Note - In Generator, prepend feat: or fix: in PR title only when PATCH/MINOR release must be triggered.

  2. PR Description: Clearly explain the issue being solved, summarize the changes made, and mention the related issue.

    Note - In Generator, we use Maintainers Work board to track progress. Ensure the PR Description includes Resolves #<issue-number> or Fixes #<issue-number> this will automatically close the linked issue when the PR is merged and helps automate the maintainers workflow.

  3. Documentation: Update the relevant Generator documentation to accurately reflect the changes introduced in the PR, ensuring users and contributors have up-to-date guidance.

  4. Comments and JSDoc: Write clear and consistent JSDoc comments for functions, including parameter types, return values, and error conditions, so others can easily understand and use the code.

  5. DRY Code: Ensure the code follows the Don't Repeat Yourself principle. Look out for duplicate logic that can be reused.

  6. Test Coverage: Ensure the new code is well-tested with meaningful test cases that pass consistently and cover all relevant edge cases.

  7. Commit History: Contributors should avoid force-pushing as much as possible. It makes it harder to track incremental changes and review the latest updates.

  8. Template Design Principles Alignment: While reviewing template-related changes in the packages/ directory, ensure they align with the Assumptions and Principles. If any principle feels outdated or no longer applicable, start a discussion these principles are meant to evolve with the project.

  9. Reduce Scope When Needed: If an issue or PR feels too large or complex, consider splitting it and creating follow-up issues. Smaller, focused PRs are easier to review and merge.

  10. Bot Comments: As reviewers, check that contributors have appropriately addressed comments or suggestions made by automated bots. If there are bot comments the reviewer disagrees with, react to them or mark them as resolved, so the review history remains clear and accurate.

Copy link

@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

🧹 Nitpick comments (1)
CODEOWNERS (1)

12-15: Optional: avoid single point of failure for packages/

If Adi is OOO, PRs touching only packages/ will request only @Adi-204. Consider adding one or more core maintainers as backup owners.

Example change within this block:

-packages/ @Adi-204
+packages/ @Adi-204 @derberg @magicmatatjahu @jonaslagoni
📜 Review details

Configuration used: Path: .coderabbit.yaml

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 5757a66 and d4892ab.

📒 Files selected for processing (1)
  • CODEOWNERS (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
  • GitHub Check: Test generator as dependency with Node 18
  • GitHub Check: Test generator as dependency with Node 20
  • GitHub Check: Acceptance tests for generated templates
  • GitHub Check: Test NodeJS PR - windows-latest
  • GitHub Check: Test NodeJS PR - ubuntu-latest
  • GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (2)
CODEOWNERS (2)

9-11: LGTM: Default owners entry is valid and well-placed

Wildcard rule is correctly specified and located before more specific patterns. No issues.


9-11: Sanity check: Code Owners + branch protection with a bot account

If “Require review from Code Owners” is enabled, ensure each effective pattern includes at least one human owner so the requirement can be satisfied. Current rules do (humans are present for *, packages/, and *.md), so this is likely fine—just confirming intent with @asyncapi-bot-eve listed.

Copy link

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

♻️ Duplicate comments (1)
CODEOWNERS (1)

12-18: *Fix precedence so Markdown under packages/ doesn’t get claimed by the later .md rule

GitHub applies “last match wins.” With packages/ defined above *.md, any packages/**/*.md will match both and end up owned by the later *.md rule, which drops @Adi-204 from reviews of template docs inside packages/. Adjust order or add an explicit override.

Option A (preferred): move the *.md block above packages/.

-# Packages directory
-# @Adi-204 is Templates Champion
-packages/ @Adi-204 @derberg @magicmatatjahu
-
-# All .md files
-# @Florence-Njeri is Docs Champion
-*.md @Florence-Njeri @derberg @asyncapi-bot-eve
+# All .md files
+# @Florence-Njeri is Docs Champion
+*.md @Florence-Njeri @derberg @asyncapi-bot-eve
+
+# Packages directory
+# @Adi-204 is Templates Champion
+packages/ @Adi-204 @derberg @magicmatatjahu

Option B: keep current order and add a specific override after the *.md rule.

 # All .md files
 # @Florence-Njeri is Docs Champion
 *.md @Florence-Njeri @derberg @asyncapi-bot-eve
+
+# Ensure Markdown under packages/ stays with Templates Champion
+packages/**/*.md @Adi-204 @derberg @magicmatatjahu

Run this quick check to see how many Markdown files live under packages/ (illustrates impact):

#!/bin/bash
set -euo pipefail
echo "CODEOWNERS (relevant lines with numbers):"
nl -ba CODEOWNERS | sed -n '1,120p'
echo
echo "Sample Markdown files under packages/:"
fd --type f --extension md packages | head -n 50
🧹 Nitpick comments (2)
CODEOWNERS (2)

12-15: Confirm intended reviewer set for packages/

packages/ owners are @Adi-204 @derberg @magicmatatjahu while default owners include @jonaslagoni @asyncapi-bot-eve too. If you want all Core Maintainers plus the Templates Champion on package changes, consider aligning.

Proposed (only if broader coverage is desired):

-packages/ @Adi-204 @derberg @magicmatatjahu
+packages/ @Adi-204 @derberg @magicmatatjahu @jonaslagoni @asyncapi-bot-eve

17-18: Optional: cover uppercase .MD files

If the repo might contain *.MD, switch to a case-insensitive bracket pattern.

-*.md @Florence-Njeri @derberg @asyncapi-bot-eve
+*.[mM][dD] @Florence-Njeri @derberg @asyncapi-bot-eve
📜 Review details

Configuration used: Path: .coderabbit.yaml

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 2c92c74 and 3fb9709.

📒 Files selected for processing (1)
  • CODEOWNERS (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Test NodeJS PR - ubuntu-latest
  • GitHub Check: Test NodeJS PR - windows-latest
  • GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (2)
CODEOWNERS (2)

20-21: *LGTM: .changeset override correctly supersedes .md

Placing .changeset/**/*.md after *.md ensures docs champions aren’t auto-requested for changesets. This ordering is correct and intentional.


9-11: Clarify scope: should @Adi-204 join the default owners as well?

PR text says “joins maintainers list as a templates champion.” If that’s scoped only to packages/, current setup is fine. If the intent is to include as a default owner, add them to *.

-* @derberg @magicmatatjahu @jonaslagoni @asyncapi-bot-eve
+* @derberg @magicmatatjahu @jonaslagoni @asyncapi-bot-eve @Adi-204

Copy link
Member

@magicmatatjahu magicmatatjahu left a comment

Choose a reason for hiding this comment

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

🚀

@sonarqubecloud
Copy link

@derberg
Copy link
Member Author

derberg commented Aug 26, 2025

/rtm

@asyncapi-bot asyncapi-bot merged commit 5bb3ce7 into asyncapi:master Aug 26, 2025
16 checks passed
@derberg
Copy link
Member Author

derberg commented Aug 26, 2025

@allcontributors please add @Adi-204 for maintainance

@allcontributors
Copy link
Contributor

@derberg

I couldn't determine any contributions to add, did you specify any contributions?
Please make sure to use valid contribution names.

@derberg
Copy link
Member Author

derberg commented Aug 26, 2025

@allcontributors please add @Adi-204 for maintenance

@allcontributors
Copy link
Contributor

@derberg

I've put up a pull request to add @Adi-204! 🎉

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants