Add BZ component name to OWNERS #367
Merged
Conversation
This file contains 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
openshift-ci-robot
added
the
approved
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sallyom, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
wking
added a commit
to wking/oc
that referenced
this pull request
Apr 17, 2020
These to subcommands interact with the cluster-version operator, which is now maintained by the updates team. I'm seeding the alias with the content from [1]. I've left the 'component' property (added to the root OWNERS in e83f2ac, Add BZ component name to OWNERS, 2020-04-03, openshift#367) off for now, because the tooling around that only consumes entries at the repo level. [1]: https://github.com/openshift/cluster-version-operator/blob/914467c03b5bc25dbe4c9295c420fdb2598db821/OWNERS
wking
added a commit
to wking/oc
that referenced
this pull request
Apr 17, 2020
This subcommand interacts with the cluster-version operator, which is now maintained by the updates team. I'm seeding the alias with the content from [1]. I've left the 'component' property (added to the root OWNERS in e83f2ac, Add BZ component name to OWNERS, 2020-04-03, openshift#367) off for now, because the tooling around that only consumes entries at the repo level. I think that the admin/release should also be maintained by the updates team, because it manages the release images for which the CVO is the sole consumer. But Scott wants to punt on that for now. [1]: https://github.com/openshift/cluster-version-operator/blob/914467c03b5bc25dbe4c9295c420fdb2598db821/OWNERS
wking
added a commit
to wking/oc
that referenced
this pull request
Apr 17, 2020
This subcommand interacts with the cluster-version operator, which is now maintained by the updates team. I'm seeding the alias with the content from [1]. I've left the 'component' property (added to the root OWNERS in e83f2ac, Add BZ component name to OWNERS, 2020-04-03, openshift#367) off for now, because the tooling around that only consumes entries at the repo level. I think that the admin/release should also be maintained by the updates team, because it manages the release images for which the CVO is the sole consumer. But Scott wants to punt on that for now. [1]: https://github.com/openshift/cluster-version-operator/blob/914467c03b5bc25dbe4c9295c420fdb2598db821/OWNERS
wking
added a commit
to wking/oc
that referenced
this pull request
Apr 17, 2020
This subcommand interacts with the cluster-version operator, which is now maintained by the updates team. I'm seeding the alias with the content from [1] (and adding Lala, who's the team lead). I've left the 'component' property (added to the root OWNERS in e83f2ac, Add BZ component name to OWNERS, 2020-04-03, openshift#367) off for now, because the tooling around that only consumes entries at the repo level. I think that the admin/release should also be maintained by the updates team, because it manages the release images for which the CVO is the sole consumer. But Scott wants to punt on that for now. [1]: https://github.com/openshift/cluster-version-operator/blob/914467c03b5bc25dbe4c9295c420fdb2598db821/OWNERS
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.
No description provided.