Create a new repo to track KubeVirt enhancements #3874
Conversation
Signed-off-by: Vladik Romanovsky <[email protected]>
kubevirt-bot
added
the
dco-signoff: yes
|
/cc @dhiller |
|
/override pull-kubevirt-org-github-config-updater Job checking the created team is failing because it can't find it - expected behaviour. |
|
@dhiller: Overrode contexts on behalf of dhiller: pull-kubevirt-org-github-config-updater In response to this:
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-sigs/prow repository. |
| - xpivarc | ||
| - vladikr | ||
| repos: | ||
| enhancements: admin |
There was a problem hiding this comment.
nit: in the long run we should cut down on this, since it is not required most of the time. IMHO write access would be enough in general, or do you have something special in mind? Maybe you should consider tide merge automation.
However all that can be done in follow ups, will not block on this.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dhiller The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubevirt-bot
added
the
approved
What this PR does / why we need it:
Following the recently accepted proposal to create a new repository to track KubeVirt enhancements kubevirt/community#362
This is a PR that aims to request this new repository.
Release note: