Repository navigation
Remove distorhead from maintainer roster - #2
Merged
ahmadqasembader merged 1 commit intoSep 14, 2026
Merged
Conversation
distorhead is listed in the .project/maintainers.yaml but is not present in the project's own OWNERS file at https://github.com/werf/werf/blob/main/OWNERS. Aligning the two rosters. Signed-off-by: Riaan Kleinhans <riaankleinhans@gmail.com>
riaankleinhans
requested review from
Fral738,
alexey-igrychev,
distorhead,
dmmordvi,
drey,
ilya-lesikov,
nervgh and
reyreavman
as code owners
August 25, 2026 20:00
Contributor
|
Merging after no response from org owners |
4 tasks done
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.
Aligning
.project/maintainers.yamlwith the project's own OWNERS file.Change: removes
distorheadfrommaintainer.This PR is part of CNCF staff's ongoing effort to reconcile
.project/maintainers.yamlfiles with each project's own maintainer file so downstream automation (mailing list sync, Jira Service Desk access, etc.) targets the correct set of maintainers.