CLP-21 Move repository ownership to Core Languages and Parsers

[aurelien-coet-sonarsource]

---

Summary by Gitar

• Repository configuration:
  • Updated .github/CODEOWNERS to transition ownership from @SonarSource/code-quality-ai-rules-issue-detection-squad to @SonarSource/code-quality-core-languages-parsers-squad.

_{This will update automatically on new commits.}

[hashicorp-vault-sonar-prod]

CLP-21

[gitar-bot]

Code Review ✅ Approved 1 resolved / 1 findings

Updates .github/CODEOWNERS to transition repository ownership, but the change fails to maintain full repository coverage previously provided by the wildcard rule.

✅ 1 resolved

✅ Quality: CODEOWNERS no longer covers the whole repository

📄 .github/CODEOWNERS:2
The previous wildcard rule * @SonarSource/code-quality-ai-rules-issue-detection-squad assigned ownership of every file in the repository. The change replaces it with .github/CODEOWNERS @SonarSource/code-quality-core-languages-parsers-squad, which only assigns ownership of the CODEOWNERS file itself. As a result, all other files in the repository now have no code owner, so PRs touching source code will no longer require review from any designated team.

Given the PR title "Move repository ownership to Core Languages and Parsers", the intent appears to be to transfer ownership of the entire repo to the new squad. If so, the rule should keep a wildcard entry pointing at the new team rather than narrowing it to just .github/CODEOWNERS.

If scoping ownership of only the CODEOWNERS file is intentional, please disregard; otherwise add a wildcard rule for the new squad.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[Wohops]

LGTM!

[sonarqube-next]

Quality Gate passed for 'sonar-rust'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube