automation: sync OWNERS_ALIASES changes from kubevirt/kubevirt and others #3530
Labels
kind/enhancement
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Yeah, I think automation around this would make much sense - not yet sure what exactly we want to do around this. I'd say we store lists inside community repo and sync from there
Originally posted by @dhiller in kubevirt/user-guide#819 (comment)
The text was updated successfully, but these errors were encountered: