Update CODEOWNERS file

[m-Peter]

Description

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the standards mentioned here.
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

Summary by CodeRabbit

• Chores
  • Updated code ownership to reflect new responsibilities.

[coderabbitai]

Walkthrough

The pull request introduces a change to the .github/CODEOWNERS file by updating the list of code owners. Specifically, the previous owner @sideninja has been replaced with @janezpodhostnik, resulting in the new roster of code owners being @janezpodhostnik, @peterargue, and @m-Peter.

Changes

File	Change Summary
.github/CODEOWNERS	Updated code owner from @sideninja to @janezpodhostnik

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant CodeOwner

    User->>GitHub: Create Pull Request
    GitHub->>CodeOwner: Notify about changes
    CodeOwner-->>GitHub: Review changes
    GitHub-->>User: Pull Request updated

Loading

Poem

🐰 In the land of code and cheer,
A new owner hops in here!
With @janezpodhostnik in the lead,
Our code will flourish, yes indeed!
So let’s all dance and play,
For changes brightened up our day! 🎉

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between e3e44ae and 5ba3dfa.

📒 Files selected for processing (1)

• .github/CODEOWNERS (1 hunks)

🔇 Additional comments (1)

.github/CODEOWNERS (1)

1-1: LGTM! Verify all intended owners are included.

The update to the CODEOWNERS file looks good. The change replaces @sideninja with @janezpodhostnik as mentioned in the PR summary, while retaining @peterargue and @m-Peter as code owners.

To ensure all intended owners are included, please run the following command:

This will display the contents of the CODEOWNERS file, allowing you to verify that all intended owners are correctly listed.

✅ Verification successful

Verified! No issues found.

The .github/CODEOWNERS file has been successfully updated to include @janezpodhostnik, @peterargue, and @m-Peter as code owners.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the list of code owners
# Expected result: The command should output the line from the CODEOWNERS file,
# allowing you to visually confirm the list of owners.

cat .github/CODEOWNERS

Length of output: 64

---

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.

[janezpodhostnik]

Thanks :)