chore: use github CODEOWNERS

[basmasking]

Fixes #420

Changes proposed in this pull request:

• CODEOWNERS for reviews
• removed the deprecated reviewers config for dependabot

@MaskingTechnology/comify

Summary by CodeRabbit

• Chores
  • Added a CODEOWNERS file to automatically assign @basmasking and @petermasking as reviewers for all pull requests.
  • Updated Dependabot configuration to stop automatically requesting specific reviewers for npm dependency update pull requests.

[coderabbitai]

Walkthrough

A CODEOWNERS file was introduced to assign @basmasking and @petermasking as code owners for the entire repository. Additionally, the Dependabot configuration was updated to remove the automatic assignment of specific reviewers for npm dependency update pull requests.

Changes

Files	Change Summary
.github/CODEOWNERS	Added CODEOWNERS file assigning @basmasking and @petermasking as code owners for all files.
.github/dependabot.yml	Removed the list of reviewers for npm ecosystem Dependabot PRs; no reviewers are now specified.

Assessment against linked issues

Objective (Issue #)	Addressed	Explanation
Add CODEOWNERS file (Use codeowners file) (#420)	✅

Poem

Two code owners now hop in with pride,
Watching o’er the code on every side.
Dependabot’s requests now less in queue,
Reviewers are free, with less to do.
The burrow’s in order, the rules are set—
A rabbit’s work is never done yet! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4622685 and 1450097.

📒 Files selected for processing (2)

• .github/CODEOWNERS (1 hunks)
• .github/dependabot.yml (0 hunks)

💤 Files with no reviewable changes (1)

• .github/dependabot.yml

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build (lts/*)

🔇 Additional comments (1)

.github/CODEOWNERS (1)

1-1: Approve ownership assignment.

The wildcard pattern correctly assigns @basmasking and @petermasking as code owners for all files in the repository.

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

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

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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud