Skip to content
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.

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

OWNERS: sync repositories OWNERS_ALIASES from k/kubevirt to target repositories #3814

Open
dhiller opened this issue Dec 10, 2024 · 1 comment
Labels
area/automation Issues and PRs concerning automation, i.e. KubeVirt job updates, KubeVirtCI bumps etc. kind/enhancement

Comments

@dhiller
Copy link
Contributor

dhiller commented Dec 10, 2024

Since k/kubevirt currently is the source of truth when it comes to OWNERS_ALIASES sig_*_approvers and sig_*_reviewers we should sync other repositories OWNERS_ALIASES files in regular intervals, so as to keep them up to date.

Suggestion:

  • create a postsubmit that kicks in after a change in k/kubevirt OWNERS_ALIASES gets merged and sync target aliases to the same state as in the source file

            How should we sync between changes here and in k/k?
            IOW, if someone is added as an approver for a SIG, would he need to also add himself to here in a different PR?
    

Originally posted by @iholder101 in kubevirt/community#360 (comment)

@dhiller
Copy link
Contributor Author

dhiller commented Dec 10, 2024

/kind enhancement
/area automation

@kubevirt-bot kubevirt-bot added kind/enhancement area/automation Issues and PRs concerning automation, i.e. KubeVirt job updates, KubeVirtCI bumps etc. labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/automation Issues and PRs concerning automation, i.e. KubeVirt job updates, KubeVirtCI bumps etc. kind/enhancement
Projects
None yet
Development

No branches or pull requests

2 participants