chore: add CODEOWNERS file to define code ownership

[mauvehed]

Introduce a CODEOWNERS file to specify that all code is currently owned by the user @mauvehed. This ensures clear ownership and responsibility for code maintenance and reviews, streamlining the collaboration process within the team.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
yourip	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 7, 2024 6:24pm

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR introduces a CODEOWNERS file to establish code ownership within the repository. The implementation is straightforward, adding a single configuration file that designates @mauvehed as the owner of all code in the repository.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Establish repository-wide code ownership configuration	Add initial CODEOWNERS file Configure @mauvehed as the owner for all code	CODEOWNERS

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @mauvehed - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider defining more granular code ownership patterns (e.g., by directory or component) to prevent potential review bottlenecks as the project grows.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}