Conversation
The whole DG team can maintain this
Contributor
There was a problem hiding this comment.
Pull request overview
Updates repository-level ownership metadata so the Dependency Graph (DG) team can maintain the repo via a GitHub team handle.
Changes:
- Replaces an individual codeowner (
@ajhenry) with the DG team owner (@github/dependency-graph-reviewers) for the default (*) ownership rule.
Show a summary per file
| File | Description |
|---|---|
| CODEOWNERS | Updates the default code owners to include the DG reviewers team. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 0
elrayle
approved these changes
Apr 10, 2026
We don't really need CODEOWNERS in this repo, since there isn't divided ownership of it.
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
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.
Since this repo doesn't have split ownership, it's easy to manage who can maintain this via the repository settings.