Update CODEOWNERS to use spire-maintainers team#7107
Draft
strideynet wants to merge 1 commit into
Draft
Conversation
Replace the individual maintainer list with the @spiffe/spire-maintainers team so ownership tracks team membership automatically and stays in sync across the SPIRE repositories. Signed-off-by: Noah Stride <noah.stride@goteleport.com>
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
1 participant
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.
Replaces the hard-coded list of individual maintainers in
CODEOWNERSwith the@spiffe/spire-maintainersteam.Pointing at the team means ownership tracks team membership automatically, so maintainers joining or leaving no longer requires a separate change to this file, and we can more trivially synchronise this list across the SPIRE repositories. This mirrors the equivalent changes to the SDKs:
This also drops the maintainer-roster and community-chair comment block, since that information is now represented by the GitHub team and would otherwise drift out of date. tbd: we're going to capture the list of maintainers as code in the spiffe/spiffe repo.