chore: use protocol-engineering team for codeowner

[gartnera]

Using a team is the correct way to do CODEOWNERS

You should request review of individuals if you would specifically like their review on a change.

Summary by CodeRabbit

• Chores
  • Updated code ownership to streamline team management by designating the @zeta-chain/protocol-engineering team as the primary code owner for specified paths.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request involve an update to the .github/CODEOWNERS file. The previous specification of individual GitHub users as code owners has been replaced with a single team reference, @zeta-chain/protocol-engineering. This change streamlines the ownership structure for the specified paths, while the assignment of the @zeta-chain/devops team for the .github directory remains unchanged.

Changes

File	Change Summary
.github/CODEOWNERS	Replaced individual users @brewmaster012, @kingpinXD, @lumtis, @ws4charlie, @skosito, and @swift1337 with team @zeta-chain/protocol-engineering as code owner. The assignment of @zeta-chain/devops for the .github directory remains unchanged.

Possibly related PRs

• chore: update codeowner #3245: This PR also modifies the .github/CODEOWNERS file, specifically changing the list of code owners, which indicates a direct connection to the changes made in the main PR.

Suggested labels

ci

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between d8e4fc7 and 7411bb4.

📒 Files selected for processing (1)

• .github/CODEOWNERS (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• .github/CODEOWNERS

---

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.

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.