Repository navigation
Update OWNERS to use steering-committee alias instead of TOC - #143
Conversation
Migrate the deprecated technical-oversight-committee owner alias to steering-committee in the root OWNERS file.
|
@dsimansk: GitHub didn't allow me to request PR reviews from the following users: knative-extensions/steering-committee. Note that only knative-extensions members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
There are empty aliases in OWNER_ALIASES, cleanup is advised. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dprotaso, dsimansk The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Summary
Migrate the deprecated
technical-oversight-committeeowner alias tosteering-committeein the root OWNERS file.The TOC and Steering Committee were combined in knative/community#1587, and the
technical-oversight-committeealias no longer exists in the org-level aliases, so this reference is dangling.Part of the migration started in knative/community#1798.
/cc @knative-extensions/steering-committee