Add CODEOWNERS file

[gaby]

This will allow github to auto assign the gofiber/maintainers team as reviewers of each new Pull Request.

Summary by CodeRabbit

• Chores
  • Established a code ownership policy, assigning all file ownership to @gofiber/maintainers.

[coderabbitai]

Walkthrough

This update introduces a new file, .github/CODEOWNERS, to the repository. The purpose of this file is to specify the team responsible for the maintenance of all files within the repository. The team assigned to this role is @gofiber/maintainers. This change ensures that any modifications or issues related to the repository are directed to the appropriate maintainers, streamlining the process of code review and management.

Changes

Files	Change Summary
.github/CODEOWNERS	Added file to assign @gofiber/maintainers as owners for all files in the repository.

🐇✨
In the realm of code, where changes abound,
A new guardian rises, without a sound.
With @gofiber/maintainers at the helm,
Each line of code, in a safer realm.
🌟 Through pull requests and issues, they weave,
Ensuring the codebase, we can believe.
🎉🐰 Cheers to the guardians, steadfast and true,
A hop, a skip, in digital dew.

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>.
  • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between b15a2e4 and 1e29d66.

Files selected for processing (1)

• .github/CODEOWNERS (1 hunks)

Additional comments: 1

.github/CODEOWNERS (1)

• 1-1: The CODEOWNERS file is correctly formatted, and the @gofiber/maintainers team is appropriately designated as the code owners for all files in the repository. This change aligns with the PR's objective to streamline the review process by automatically assigning the designated team to evaluate new contributions.