Skip to content

ci-operator/step-registry: Dedup OWNERS with symlinks again #12832

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
openshift-merge-robot merged 1 commit into from
Oct 23, 2020
Merged

ci-operator/step-registry: Dedup OWNERS with symlinks again #12832

openshift-merge-robot merged 1 commit into from
Oct 23, 2020

Conversation

@wking
Copy link
Member

@wking wking commented Oct 14, 2020

Like 0a90079 (#9739), picking up all the dups that have crept in since then. Generated with:

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

@wking
ci-operator/step-registry: Dedup OWNERS with symlinks again
f583eb8 
Like 0a90079 (ci-operator/step-registry: Dedup OWNERS with
symlinks, 2020-06-17, openshift#9739), picking up all the dups that have crept
in since then.  Generated with:

  $ hack/dedup-owners.sh ci-operator/step-registry
@wking wking mentioned this pull request Oct 14, 2020
Closed
@pierreprinetti
Copy link
Member

pierreprinetti commented Oct 15, 2020

/approve

@wking wking mentioned this pull request Oct 20, 2020
Merged
@wking
Copy link
Member Author

wking commented Oct 20, 2020

/assign @praveenkumar @stbenjam @tmckayus

@stbenjam
Copy link
Member

stbenjam commented Oct 21, 2020

/approve

1 similar comment
@tmckayus
Copy link
Contributor

tmckayus commented Oct 21, 2020

/approve

@wking
Copy link
Member Author

wking commented Oct 22, 2020

/assign @praveenkumar

Looks like you're the only one who still needs to sign off on this.

@praveenkumar
Copy link
Contributor

praveenkumar commented Oct 23, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2020
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 23, 2020

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierreprinetti, praveenkumar, stbenjam, tmckayus, 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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 23, 2020
@openshift-merge-robot openshift-merge-robot merged commit f6763e9 into openshift:master Oct 23, 2020
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 23, 2020

@wking: Updated the following 2 configmaps:

  • step-registry configmap in namespace ci at cluster api.ci using the following files:
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/assisted/setup/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/check/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/crc/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/snc/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/snc/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/snc/e2e/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/openstack/precheck/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/stableinitial/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/openstack/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/openstack/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/crc/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/upi/xpn/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/openstack/ipi/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/vsphere/upi/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/upgrade/aws/loki/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/upgrade/azure/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/creatednsrecords/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/createfips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/generateconfig/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/deprovision/deletednsrecords/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/deprovision/deletefips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/operatorhub/subscribe/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/conf/gcp/xpn/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/conf/vsphere/ova/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/nested/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/nested/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/xpn/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/xpn/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/xpn/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/vsphere/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/vsphere/pre/OWNERS
  • 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/baremetalds/assisted/setup/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/devscripts/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/e2e/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/baremetalds/packet/check/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/crc/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/snc/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/snc/e2e/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/code-ready/snc/e2e/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/conf/openstack/precheck/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/install/stableinitial/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/openstack/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/ipi/openstack/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/crc/test/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/gcp/upi/xpn/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/openstack/ipi/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/e2e/vsphere/upi/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/upgrade/aws/loki/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openshift/upgrade/azure/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/creatednsrecords/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/createfips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/conf/generateconfig/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/deprovision/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/deprovision/deletednsrecords/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/openstack/deprovision/deletefips/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/operatorhub/subscribe/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/conf/gcp/xpn/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/conf/vsphere/ova/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/nested/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/nested/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/xpn/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/xpn/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/gcp/xpn/pre/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/vsphere/post/OWNERS
    • key OWNERS using file ``
    • key OWNERS using file ci-operator/step-registry/upi/vsphere/pre/OWNERS
Details

In response to this:

Like 0a90079 (#9739), picking up all the dups that have crept in since then. 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-again branch October 23, 2020 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@adduarte adduarte Awaiting requested review from adduarte

@pierreprinetti pierreprinetti Awaiting requested review from pierreprinetti

Assignees

@praveenkumar praveenkumar

@stbenjam stbenjam

@tmckayus tmckayus

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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

7 participants

@wking @pierreprinetti @stbenjam @tmckayus @praveenkumar @openshift-ci-robot @openshift-merge-robot