Indicates a PR has been approved by an approver from all required OWNERS files.

area/api-server

area/controller

area/instancetype

area/monitoring

Denotes a PR to master as a candidate for cherry picking into a release branch.

dco-signoff: no

Indicates the PR's author has not DCO signed all their commits.

dco-signoff: yes

Indicates the PR's author has DCO signed all their commits.

Pull requests that update a dependency file

distro/kubernetes

distro/openshift

do-not-merge/hold

Indicates that a PR should not merge because someone has issued a /hold command.

do-not-merge/invalid-commit-message

do-not-merge/invalid-owners-file

do-not-merge/release-note-label-needed

Indicates that a PR should not merge because it's missing one of the release note labels.

do-not-merge/work-in-progress

Indicates that a PR should not merge because it is a work in progress.

good first issue

Identifies an issue that has been specifically created or selected for first-time contributors.

good-first-issue

Identifies an issue that has been specifically created or selected for first-time contributors.

Categorizes as a Hacktoberfest contribution

Identifies an issue that has been specifically created or selected for new contributors.

kind/api-change

Categorizes issue or PR as related to adding, removing, or otherwise changing an API

kind/build-change

Categorizes PRs as related to changing build files of virt-* components

Categorizes issue or PR as related to cleaning up code, process, or technical debt.

kind/deprecation

Indicates the PR/issue deprecates a feature that will be removed in a subsequent release.

kind/enhancement

kind/failing-test

Categorizes issue or PR as related to a failing test.

Categorizes issue or PR as related to a flaky test.

Indicates that a PR is ready to be merged.

lifecycle/active

Indicates that an issue or PR is actively being worked on by a contributor.

lifecycle/frozen

Indicates that an issue or PR should not be auto-closed due to staleness.

lifecycle/rotten

Denotes an issue or PR that has aged beyond stale and will be auto-closed.

lifecycle/stale

Denotes an issue or PR has remained open with no activity and has become stale.

needs/documentation

needs-approver-review

Indicates that a PR requires a review from an approver.

needs-ok-to-test

Indicates a PR that requires an org member to verify it is safe to test.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Indicates a non-member PR verified by an org member that is safe to test.

priority/backlog

Indicate that the issue or PR is a lower priority and can be worked on in the future

priority/critical-urgent

Categorizes an issue or pull request as critical and of urgent priority.

release-blocker/cancel

release-blocker/fake

release-blocker/main

release-blocker/master

release-blocker/release-0.29

release-blocker/release-0.32

release-blocker/release-0.33

release-blocker/release-0.34

release-blocker/release-0.36

release-blocker/release-0.40

release-blocker/release-0.41

release-blocker/release-0.56

release-blocker/release-0.59

release-blocker/release-1.2

release-blocker/release-1.3

release-blocker

Indicates that a PR or issue is blocking a release from a specific branch.

Denotes a PR that will be considered when it comes time to generate release notes.

release-note-action-required

Denotes a PR that introduces potentially breaking changes that require user action.

release-note-none

Denotes a PR that doesn't merit a release note.

research-needed

Denotes an issue or PR that relates to changes in api.

sig/buildsystem

Denotes an issue or PR that relates to changes in the build system.

Denotes an issue or PR as being related to sig-ci, marks changes to the CI system.

sig/documentation

sig/observability

Denotes an issue or PR that relates to observability.

Categorizes issues or PRs as an invalid contribution

topic/community

topic/documentation

topic/infrastructure

topic/integration

topic/packaging

topic/performance

topic/scheduling

triage/accepted

Indicates an issue or PR is ready to be actively worked on.

triage/build-watcher

triage/duplicate

Indicates an issue is a duplicate of other open issue.

triage/infra-issue

Indicates an issue was caused by failures in the infrastructure.

triage/needs-information

Indicates an issue needs more information in order to work on it.

triage/not-reproducible

Indicates an issue can not be reproduced as described.

triage/unresolved

Indicates an issue that can not or will not be resolved.

Denotes an issue or PR that relates to the ARM architecture working group.

Denotes an issue or PR that relates to the s390x architecture working group.

wg/code-quality

Denotes an issue or PR that relates to the code-quality working group.

Please see https://github.com/kubevirt/community/blob/main/sig-network/charter.md

No labels found. Sorry about that.