Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-74101

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

XMLWordPrintable

    • kubevirt_sync_OWNERS_ALIASES
    • Quality / Stability / Reliability
    • 77
    • False
    • Hide

      None

      Show
      None
    • False
      • Postsubmit job triggers on k/kubevirt OWNERS_ALIASES changes
      • OWNERS_ALIASES synced to k/community, k/user-guide, k/enhancements
      • Sync PRs created automatically in target repositories
    • None
    • Green
    • To Do
    • 100% To Do, 0% In Progress, 0% Done
    • Hide

      2026-02-16:
      on track on CNV v4.22.0...

      Show
      2026-02-16: on track on CNV v4.22.0...

      Goal

      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.

      https://github.com/kubevirt/project-infra/issues/3814

      User Stories

      • repositories to sync with k/kubevirt are
        • k/community
        • k/user-guide
        • k/enhancements
      • 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

      Non-Requirements

      • List of things not included in this epic, to alleviate any doubt raised during the grooming process.

      Notes

      • Any additional details or decisions made/needed

              dhiller72 Daniel Hiller
              dhiller72 Daniel Hiller
              Daniel Hiller Daniel Hiller
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: