feat: Add JUnit codeowners annotation - #202
Draft
ivan-mmllc wants to merge 3 commits into
Draft
Conversation
mvpowers
approved these changes
Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related PR(s)
Related Issue(s)
Summary / Background
We currently have JUnit test reports the tell us if a test fails, but we want to have codeowners attached to these tests to surface the issue to the correct team.
For JUnit test reports, we want to have codeowners-plus read and annotate codeowners into the test reports. This PR adds support for annotating test reports generated by jest and pytest.
The PR adds a JUnit option to the codeowners-cli to print codeowners information for test reports in stdout. The PR also adds a new action to automatically write annotated codeowners to a new test report file.