Permalink
Fetching contributors…
Cannot retrieve contributors at this time
123 lines (107 sloc) 23.3 KB

Kubernetes GitHub Labels

Intro

These file was auto generated by the label_sync tool, based on the labels.yaml that it uses to sync github labels across repos in the kubernetes github org

Why these labels?

The rule of thumb is that labels are here because they are intended to be produced or consumed by our automation (primarily prow) across all repos. There are some labels that can only be manually applied/removed, and where possible we would rather remove them or add automation to allow a larger set of contributors to apply/remove them.

How do I add a new label?

  • Add automation that consumes/produces the label
  • Open a PR against labels.yaml
  • Involve sig-contributor-experience in the change, eg: chat about it in slack, mention @kubernetes/sig-contributor-experience-pr-reviews in the PR, etc.
  • After the PR is merged, a kubernetes CronJob is responsible for syncing labels daily

Labels that apply to both issues and PRs

Name Description Added By Prow Plugin
triage/duplicate Indicates an issue is a duplicate of other open issue. The usage should be supported by adding triage findings as an issue comment.

This was previously close/duplicate,
humans
triage/needs-information Indicates an issue needs more information in order to work on it. The usage should be supported by adding triage findings as an issue comment.

This was previously close/needs-information,
humans
triage/not-reproducible Indicates an issue can not be reproduced as described. The usage should be supported by adding triage findings as an issue comment.

This was previously close/not-reproducible,
humans
triage/unresolved Indicates an issue that can not be resolved. The usage should be supported by adding triage findings as an issue comment.

This was previously close/unresolved,
humans
committee/conduct Denotes an issue or PR intended to be handled by the (as of yet non-existent) code of conduct committee. anyone label
committee/steering Denotes an issue or PR intended to be handled by the kubernetes steering committee. anyone label
kind/bug Categorizes issue or PR as related to a bug. anyone label
kind/documentation Categorizes issue or PR as related to documentation. anyone label
kind/feature Categorizes issue or PR as related to a new feature. anyone label
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

This was previously keep-open,
anyone lifecycle
lifecycle/rotten Denotes an issue or PR that has aged beyond lifecycle/stale and will be auto-closed. anyone or @fejta-bot via periodic-test-infra-rotten prowjob lifecycle
lifecycle/stale Denotes an issue or PR has remained open with no activity for too long and has become stale.

This was previously stale,
anyone or @fejta-bot via periodic-test-infra-stale prowjob lifecycle
priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. These are mostly place-holders for potentially good ideas, so that they don't get completely forgotten, and can be referenced /deduped every time they come up. anyone label
priority/backlog Higher priority than priority/awaiting-more-evidence. There appears to be general agreement that this would be good to have, but we may not have anyone available to work on it right now or in the immediate future. Community contributions would be most welcome in the mean time (although it might take a while to get them reviewed if reviewers are fully occupied with higher priority issues, for example immediately before a release). anyone label
priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. Stuff is burning. If it's not being actively worked on, someone is expected to drop what they're doing immediately to work on it. Team leaders are responsible for making sure that all the issues, labeled with this priority, in their area are being actively worked on. Examples include user-visible bugs in core features, broken builds or tests and critical security issues. anyone label
priority/failing-test Automatically filed frequently failing test. Needs to be investigated. We would like to migrate/replace this with kind/failing test (kubernetes/community#1579) anyone label
priority/important-longterm Important over the long term, but may not be currently staffed and/or may require multiple releases to complete. anyone label
priority/important-soon Lower priority than priority/critical-urgent. Must be staffed and worked on either currently, or very soon, ideally in time for the next release. anyone label
sig/api-machinery Categorizes an issue or PR as relevant to sig-api-machinery. anyone label
sig/apps Categorizes an issue or PR as relevant to sig-apps. anyone label
sig/architecture Categorizes an issue or PR as relevant to sig-architecture. anyone label
sig/auth Categorizes an issue or PR as relevant to sig-auth. anyone label
sig/autoscaling Categorizes an issue or PR as relevant to sig-autoscaling. anyone label
sig/aws Categorizes an issue or PR as relevant to sig-aws. anyone label
sig/azure Categorizes an issue or PR as relevant to sig-azure. anyone label
sig/big-data Categorizes an issue or PR as relevant to sig-big-data. anyone label
sig/cli Categorizes an issue or PR as relevant to sig-cli. anyone label
sig/cluster-lifecycle Categorizes an issue or PR as relevant to sig-cluster-lifecycle. anyone label
sig/cluster-ops Categorizes an issue or PR as relevant to sig-cluster-ops. anyone label
sig/contributor-experience Categorizes an issue or PR as relevant to sig-contributor-experience. anyone label
sig/docs Categorizes an issue or PR as relevant to sig-docs. anyone label
sig/gcp Categorizes an issue or PR as relevant to sig-gcp. anyone label
sig/ibmcloud Categorizes an issue or PR as relevant to sig-ibmcloud. anyone label
sig/instrumentation Categorizes an issue or PR as relevant to sig-multicluster. anyone label
sig/multicluster Categorizes an issue or PR as relevant to sig-multicluster.

This was previously sig/federation, sig/federation (deprecated - do not use),
anyone label
sig/network Categorizes an issue or PR as relevant to sig-network. anyone label
sig/node Categorizes an issue or PR as relevant to sig-node. anyone label
sig/onprem Categorizes an issue or PR as relevant to sig-onprem. anyone label
sig/openstack Categorizes an issue or PR as relevant to sig-openstack. anyone label
sig/release Categorizes an issue or PR as relevant to sig-release. anyone label
sig/scalability Categorizes an issue or PR as relevant to sig-scalability. anyone label
sig/scheduling Categorizes an issue or PR as relevant to sig-scheduling. anyone label
sig/service-catalog Categorizes an issue or PR as relevant to sig-service-catalog. anyone label
sig/storage Categorizes an issue or PR as relevant to sig-storage. anyone label
sig/testing Categorizes an issue or PR as relevant to sig-testing. anyone label
sig/ui Categorizes an issue or PR as relevant to sig-ui. anyone label
sig/vmware Categorizes an issue or PR as relevant to sig-vmware. anyone label
sig/windows Categorizes an issue or PR as relevant to sig-windows. anyone label
status/approved-for-milestone Used during release burndown. Denotes an issue or PR is approved to be part of the release, aka in the milestone. A bot will warn then kick issues out of the milestone that lack this label.

This was previously approved-for-milestone,
@kubernetes/kubernetes-milestone-maintainers milestonestatus
status/in-progress Used during release burndown. Denotes that an issue is actively being worked. @kubernetes/kubernetes-milestone-maintainers milestonestatus
status/in-review Used during release burndown. Denotes that a fix for an issue is actively being reviewed. @kubernetes/kubernetes-milestone-maintainers milestonestatus

Labels that apply to only PRs

Name Description Added By Prow Plugin
approved Indicates a PR has been approved by an approver from all required OWNERS files. approvers approve
cherrypick-approved Indicates a cherrypick PR into a release branch has been approved by the release branch manager. Consumed by the kubernetes/kubernetes cherrypick-queue. humans
cherrypick-candidate Denotes a PR to master as a candidate for cherry picking into a release branch. humans
cla: human-approved REMOVING. This will be deleted after 2018-04-16 00:00:00 +0000 UTC

This is a holdover from when we had difficulties getting either the google or cncf CLA bots to behave. It can only be manually applied and is consumed by the submit-queue. It has seen very little use lately.
humans
cncf-cla: no Indicates the PR's author has not signed the CNCF CLA according to the CNCF CLA bot. prow cla
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA according to the CNCF CLA bot. prow cla
do-not-merge DEPRECATED. Indicates that a PR should not be merged. The label can only be manually applied/removed. Please use do-not-merge/hold instead. humans
do-not-merge/blocked-paths Indicates that a PR should not be merged because it touches files in blocked paths. prow blockade
do-not-merge/cherry-pick-not-approved Indicates that a PR should not be merged into a release branch because the cherrypick-approved label is not present. mungegithub cherrypick-label-unapproved munger
do-not-merge/hold Indicates that a PR should not be merged because someone has issued a /hold command, applied by the prow hold plugin. anyone hold
do-not-merge/release-note-label-needed Indicates that a PR should not be merged because it's missing one of the release note labels that specify whether this PR should be considered when release notes are generated.

This was previously release-note-label-needed,
prow releasenote
do-not-merge/work-in-progress Indicates that a PR should not be merged because it is a work in progress, based on the presence of a '[wip]' prefix in the PR title. prow wip
lgtm Indicates that a PR is ready to be merged. reviewers or members lgtm
needs-ok-to-test Indicates a PR has been submitted by an untrusted contributor, and requires an org member to verify the PR is safe to test. This is to prevent spam/abuse of our CI system, and can be circumvented by becoming an org member. Org members can remove this label with the /ok-to-test command. prow trigger
needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. Rebase the PR, resolving any merge conflicts, and push the PR to remove the label. prow needs-rebase
queue/blocks-others DEPRECATED. Bumps a PR up in priority in the submit-queue for kubernetes/kubernetes because that PR blocks others by being a dependency for other pending changes. This will stop having any effect once kubernetes/kubernetes migrates away from the submit queue. humans
queue/critical-fix DEPRECATED. Bumps a PR up in priority in the submit-queue for kubernetes/kubernetes because that PR that contains a critical fix, and will merge even if e2e tests are failing. This will stop having any effect once kubernetes/kubernetes migrates away from the submit queue. humans
queue/fix DEPRECATED. Bumps a PR up in priority in the submit-queue for kubernetes/kubernetes because that PR that will fix or unblock the submit queue. This will stop having any effect once kubernetes/kubernetes migrates away from the submit queue. humans
queue/multiple-rebases DEPRECATED. Bumps a PR up in priority in the submit-queue for kubernetes/kubernetes because that PR that has had difficulty getting merged because merges ahead of it have forced it to be rebased multiple times. This will stop having any effect once kubernetes/kubernetes migrates away from the submit queue. humans
release-note Denotes a PR that will be considered when it comes time to generate release notes. prow releasenote
release-note-action-required Denotes a PR that introduces potentially breaking changes that necessitate user action before upgrading to the release that includes these changes. These actions will be specifically called out when it comes time to generate release notes. prow releasenote
release-note-none Denotes a PR that doesn't merit a release note, and will be ignored when it comes time to generate release notes. prow or member or author releasenote
retest-not-required Indicates that a PR doesn't need to be retested prior to merge. At present only submit-queue consumes this label. Unclear whether we're going to modify tide to respect this or not (kubernetes/test-infra#5334) humans
retest-not-required-docs-only Indicates that a PR doesn't need to be retested prior to merge because it only changes docs. At present only submit-queue consumes this label. Unclear whether we're going to modify tide to respect this or not (kubernetes/test-infra#7195) prow docs-no-retest
size/L Denotes a PR that changes 100-499 lines, ignoring generated files. prow size
size/M Denotes a PR that changes 30-99 lines, ignoring generated files. prow size
size/S Denotes a PR that changes 10-29 lines, ignoring generated files. prow size
size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. prow size
size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. prow size
size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. prow size

Labels that apply to only issues

Name Description Added By Prow Plugin
help wanted Denotes an issue ready for a new contributor according to the [help-wanted] guidelines, applied in response to /help by the help prow plugin.

This was previously help-wanted, for-new-contributors,
anyone help
needs-sig Indicates an issue lacks a sig/foo label and requires one. The label will be removed when a sig/ label is applied. prow requiresig