ci: add codeowners

[MSevey]

Overview

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

Summary by CodeRabbit

• Chores

  • Updated the code owners for more efficient pull request reviews.
  • Modified the auto request review configuration to reflect changes in the review teams.

• Documentation

  • Adjusted file matching patterns for Dockerfiles and GitHub-related files in review settings.

• Tests

  • Temporarily disabled the unit testing workflow, indicating a shift in testing strategy.

[coderabbitai]

Walkthrough

The project's GitHub repository has been updated to refine the code review process and adjust the testing workflow. Code ownership has been reassigned, affecting who reviews pull requests. The unit testing workflow has been disabled, hinting at a shift in how the project approaches testing.

Changes

File Path	Change Summary
.github/CODEOWNERS	Added global code owners and assigned specific owners to the .github directory.
.github/auto_request_review.yml	Updated reviewer groups and file matching patterns; set ignore_draft to true.
.github/workflows/test.yml	Disabled the unit testing process and replaced it with an echo statement.

🐇 In the fall, we hop and tweak, 🍂
Code guardians shift, as new paths we seek.
Tests rest for a spell, in silence they speak,
Awaiting the dawn of the strategy we peek. 🌅

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

Note: For conversation with the bot, please use the review comments on code diffs or files.

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

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 85b9eaa and 18b077f.

Files selected for processing (2)

• .github/CODEOWNERS (1 hunks)
• .github/auto_request_review.yml (2 hunks)

Files skipped from review due to trivial changes (1)

• .github/CODEOWNERS

Additional comments: 4

.github/auto_request_review.yml (4)

• 3-9: The changes in the code-owners and rollkit groups look good, but ensure that the team members are aware of their new responsibilities and that the previous responsibilities of "Nashqueue" are fully transferred to "Manav-Aggarwal".

• 15-18: The addition of "MSevey" to the devops group should be communicated to the team, and it should be ensured that "MSevey" is aware of the new responsibilities. Also, verify that the devops group is the correct group for "MSevey" to be added to, as the context suggests they were added to the "rollkit" group in the summary.

• 22-30: The file patterns for automatic review requests have been updated correctly to include the code-owners group for all files and specifically for Dockerfiles and GitHub-related files. This should ensure that the right people are notified for reviews on changes to these files.

• 32-32: The ignore_draft option is set to true, which is a good practice to avoid unnecessary review requests for work-in-progress changes. However, ensure that all contributors are aware of this change so they can mark their pull requests as drafts if they are not ready for review.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 18b077f and 5484dd7.

Files selected for processing (1)

• .github/workflows/test.yml (1 hunks)