ci: update update-maintainers-trigger.yaml workflow from global .github repo

[asyncapi-bot]

Summary by CodeRabbit

• New Features
  • Introduced a GitHub Actions workflow to automatically update the MAINTAINERS.yaml file based on changes to CODEOWNERS files.
• Documentation
  • Added comments to clarify the purpose and management of the new workflow.

[netlify]

✅ Deploy Preview for asyncapi-website ready!

Name	Link
🔨 Latest commit	7c8c52a
🔍 Latest deploy log	https://app.netlify.com/sites/asyncapi-website/deploys/67334486d37e6100081fa0ad
😎 Deploy Preview	https://deploy-preview-3382--asyncapi-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[coderabbitai]

Warning

Rate limit exceeded

@asyncapi-bot has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 45 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 9291da3 and 7c8c52a.

Walkthrough

The changes introduce a new GitHub Actions workflow file named update-maintainers-trigger.yaml. This workflow is designed to automatically trigger an update to the MAINTAINERS.yaml file whenever modifications are made to specified CODEOWNERS files in the repository. It activates on pushes to the master branch and monitors changes in three directories: the root, .github, and .docs. The workflow consists of a single job that uses the repository-dispatch action to send an event to the community repository.

Changes

File Path	Change Summary
.github/workflows/update-maintainers-trigger.yaml	New workflow file added to trigger updates to MAINTAINERS.yaml based on changes to CODEOWNERS files.

Possibly related PRs

• docs(community): update latest maintainers list #3273: This PR updates the MAINTAINERS.json file, which is directly related to the MAINTAINERS.yaml file being updated in the main PR.
• docs(community): update latest maintainers list #3291: Similar to docs(community): update latest maintainers list #3273, this PR also updates the MAINTAINERS.json file, indicating changes to maintainers that may be relevant to the workflow introduced in the main PR.
• docs(community): update latest maintainers list #3361: This PR modifies the MAINTAINERS.json file, reflecting updates to the maintainers' information, which aligns with the purpose of the main PR's workflow.
• docs(community): update latest maintainers list #3377: This PR updates the MAINTAINERS.json file, focusing on the maintainers' availability and company affiliations, which is relevant to the workflow changes in the main PR.

Suggested reviewers

• derberg
• akshatnema
• magicmatatjahu
• anshgoyalevil
• Mayaleeeee
• devilkiller-ag
• sambhavgupta0705
• asyncapi-bot-eve

Poem

🐰 In the garden of code, a new path we weave,
With workflows that trigger, and changes to leave.
When CODEOWNERS are touched, the magic will flow,
Updating the maintainers, as we all know!
So hop with delight, for the changes are here,
A dance of automation, let’s give a cheer! 🎉

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

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

Documentation and Community

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 67.77%. Comparing base (9291da3) to head (7c8c52a).
Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3382   +/-   ##
=======================================
  Coverage   67.77%   67.77%           
=======================================
  Files          21       21           
  Lines         664      664           
=======================================
  Hits          450      450           
  Misses        214      214           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[asyncapi-bot]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🔴 Performance	42
🟢 Accessibility	98
🟢 Best practices	92
🟢 SEO	100
🔴 PWA	33

Lighthouse ran on https://deploy-preview-3382--asyncapi-website.netlify.app/