project-infra icon indicating copy to clipboard operation
project-infra copied to clipboard

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

Open dhiller opened this issue 11 months ago • 2 comments

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 https://github.com/kubevirt/community/pull/360#discussion_r1867283347

dhiller avatar Dec 10 '24 12:12 dhiller

/kind enhancement /area automation

dhiller avatar Dec 10 '24 12:12 dhiller

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot avatar Mar 10 '25 13:03 kubevirt-bot

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubevirt-bot avatar Apr 09 '25 13:04 kubevirt-bot

Very important IMO

/remove-lifecycle rotten

iholder101 avatar Apr 10 '25 07:04 iholder101

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot avatar Jul 09 '25 07:07 kubevirt-bot

/remove-lifecycle stale

iholder101 avatar Jul 09 '25 08:07 iholder101

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot avatar Oct 07 '25 08:10 kubevirt-bot