Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Apr 29, 2022

Like 0a90079 (#9739) and 9c1d14a (#25574), picking up all the dups that have crept in since the most recent round, possibly 9c1d14a. Generated with:

$ hack/dedup-owners.sh ci-operator/step-registry

Like 0a90079 (ci-operator/step-registry: Dedup OWNERS with
symlinks, 2020-06-17, openshift#9739) and 9c1d14a
(ci-operator/step-registry: Dedup OWNERS with symlinks again,
2022-01-24, openshift#25574), picking up all the dups that have crept in since
the most recent round, possibly 9c1d14a.  Generated with:

  $ hack/dedup-owners.sh ci-operator/step-registry
@openshift-ci openshift-ci bot requested review from bertinatto and clnperez April 29, 2022 20:36
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 2, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 2, 2022

@wking: all tests passed!

Full PR test history. Your PR dashboard.

Details

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/test-infra repository. I understand the commands that are listed here.

@openshift-merge-robot openshift-merge-robot merged commit a68bce2 into openshift:master May 2, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 2, 2022

@wking: Updated the step-registry configmap in namespace ci at cluster app.ci using the following files:

  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/agent/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/baremetal/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/baremetal/operator/capi/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/baremetal/operator/catalog-publish/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/common/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/common/setup/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/common/setup/post/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/common/setup/prepare/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/common/setup/test/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/publish-python-client/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/verify-generated-code/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/setup/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/setup/configure/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/setup/machine/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/setup/prejob-cleanup/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/setup/template/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/teardown/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/assisted/vsphere/teardown/machine/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws-load-balancer/install/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws-load-balancer/pre-install/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/deprovision/cco-manual-users/static/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/deprovision/s3buckets/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/deprovision/stacks/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/provision/bastionhost/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/provision/cco-manual-users/static/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/provision/vpc/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/aws/provision/vpc/shared/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/azure/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/azure/deprovision/resourcegroup/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/azure/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/azure/provision/bastionhost/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/azure/provision/nat/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/azure/provision/resourcegroup/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/azure/provision/vnet/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/check/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/aws/ipi/disconnected/private/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/aws/ipi/private/cco-manual-security-token-service/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/aws/ipi/private/cco-manual-security-token-service/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/aws/ipi/proxy/cco-manual-security-token-service/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/aws/ipi/proxy/cco-manual-security-token-service/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/disconnected-proxy/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/disconnected-proxy/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/disconnected-proxy/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/disconnected/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/disconnected/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/private/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/private/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/private/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/ipi/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/upi/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/upi/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/gcp/upi/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/disconnected/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/disconnected/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/ovn/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/ovn/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/ovn/ipsec/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/ovn/ipsec/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/ovn/ipsec/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/ovn/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/ipi/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/upi/disconnected/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/cucushift/installer/rehearse/vsphere/upi/disconnected/secureboot/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/gcp/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/gcp/deprovision/bastionhost/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/gcp/deprovision/vpc/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/gcp/provision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/gcp/provision/bastionhost/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/gcp/provision/vpc/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/ipi/deprovision/deprovision/powervs/deprovision/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/ipi/ibmcloud/gather-resources/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/ipi/install/powervs/install/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/ipi/powervs/gather-resources/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/ipi/powervs/post/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/ipi/powervs/pre/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/konveyor/install-openshift-pipelines-operator/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/mirror-images/by-oc-adm/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/aws/single-node/workers/upgrade-conformance/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/aws/single-node/workers/upgrade-conformance/test/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/aws/upi/proxy/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/csi/migration/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/openstack/hwoffload/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openshift/e2e/openstack/sriov/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openstack/provision/config-drive/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/openstack/provision/sriov-networknodepolicy/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/operatorhub/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/proxy/config-generate/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/redhat-et/microshift/e2e/copr-install/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/redhat-et/microshift/e2e/wait-for-ssh/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/storage/conf/csi-openstack-cinder/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/storage/conf/csi-openstack-manila/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/telco5g/cnf-tests/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/aws/post/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/aws/pre/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/aws/proxy/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/aws/proxy/post/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/aws/proxy/pre/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/conf/aws/proxy/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/deprovision/aws/check-destroy/OWNERS
  • key OWNERS using file ``
  • key OWNERS using file ci-operator/step-registry/upi/install/aws/cluster/OWNERS
Details

In response to this:

Like 0a90079 (#9739) and 9c1d14a (#25574), picking up all the dups that have crept in since the most recent round, possibly 9c1d14a. Generated with:

$ hack/dedup-owners.sh ci-operator/step-registry

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/test-infra repository.

@wking wking deleted the dedup-step-owners branch May 2, 2022 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants