Skip to content

CODEOWNERS: make language coverage team responsible for more Rust and C++ code - #22276

Open
jketema wants to merge 2 commits into
github:mainfrom
jketema:jketema/own
Open

CODEOWNERS: make language coverage team responsible for more Rust and C++ code#22276
jketema wants to merge 2 commits into
github:mainfrom
jketema:jketema/own

Conversation

@jketema

@jketema jketema commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@jketema
jketema requested a review from asgerf August 4, 2026 14:28
@jketema
jketema marked this pull request as ready for review August 4, 2026 14:28
@jketema
jketema requested a review from a team as a code owner August 4, 2026 14:28
Copilot AI balanced review requested due to automatic review settings August 4, 2026 14:28
asgerf
asgerf previously approved these changes Aug 4, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Extends language-coverage ownership to shared C++/Rust infrastructure and unified extractor components.

Changes:

  • Adds coverage-team ownership for shared C++ and Yeast code.
  • Adds coverage-team ownership for unified extractor components.
Show a summary per file
File Description
CODEOWNERS Expands language-coverage team ownership patterns.

Review details

  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Balanced

Comment thread CODEOWNERS Outdated
Comment on lines +27 to +30
/shared/cpp @github/code-scanning-language-coverage
/shared/yeast @github/code-scanning-language-coverage
/shared/yeast-macros @github/code-scanning-language-coverage
/shared/yeast-schema @github/code-scanning-language-coverage

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's exactly the idea Copilot, as this is noise for the library reviewers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants