chore: update CODEOWNERS

[JivusAyrus]

Summary by CodeRabbit

• Chores
  • Updated code ownership configuration for repository maintenance and team assignments across multiple directories.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Checklist

• I have discussed my proposed changes in an issue and have received approval to proceed.
• I have followed the coding standards of the project.
• Tests or benchmarks have been added or updated.
• Documentation has been updated on https://github.com/wundergraph/cosmo-docs.
• I have read the Contributors Guide.

[coderabbitai]

Walkthrough

Updates the .github/CODEOWNERS file to modify ownership assignments. Adds thisisnithin as owner for /composition/ and /composition-go/ directories. Removes miklosbarabas from graphqlmetrics/, helm/, and infrastructure ownership sections while preserving other existing owner assignments.

Changes

Cohort / File(s)	Summary
Ownership configuration .github/CODEOWNERS	Adds thisisnithin to /composition/ and /composition-go/ ownership. Removes miklosbarabas from graphqlmetrics/, helm/, and infrastructure ownership. Preserves all other ownership assignments.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Simple metadata changes to codeowner assignments with no logic or functional impact

Possibly related PRs

• chore(github): add CODEOWNERS file and remove pr-description workflow #1998: Both PRs modify .github/CODEOWNERS file; the related PR initially added the file while this PR adjusts specific ownership entries.

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'chore: update CODEOWNERS' is vague and doesn't specify the main change of adding @thisisnithin as an owner.	Consider using a more specific title like 'chore: add @thisisnithin as CODEOWNER for composition directories' to clearly communicate the key change.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.github/CODEOWNERS (2)

1-1: Optional: fix minor typo in top-level comment

The word “expections” in the header comment appears to be a typo; consider changing it to “exceptions” for clarity.

---

9-9: Optional: remove duplicate owner on /cli/ line

@endigma appears twice on the /cli/ entry. It’s harmless but redundant; consider keeping it only once.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c914f13 and 0ebc4cf.

📒 Files selected for processing (1)

• .github/CODEOWNERS (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Analyze (go)

🔇 Additional comments (2)

.github/CODEOWNERS (2)

10-11: Composition ownership updates look correct

The additions of @thisisnithin to /composition/ and /composition-go/ are syntactically valid and consistent with the rest of the CODEOWNERS file and the stated PR goal. No further changes needed here.

---

15-17: Confirm reduced owner sets for infra/metrics/helm/otel paths

The updated entries for /graphqlmetrics/, /helm/, /infrastructure/, and /otelcollector/ are syntactically valid and still have clear ownership, but they significantly narrow the responsible set of reviewers. Please just confirm this reduced owner list matches the agreement you reached with the team.

Also applies to: 19-19

[StarpTech]

LGTM