Skip to content

Latest commit

 

History

History
124 lines (102 loc) · 13.7 KB

labels.md

File metadata and controls

124 lines (102 loc) · 13.7 KB
Raw

Open Services Group GitHub Labels

Table of Contents

Intro

This file was auto generated by the label_sync tool, based on the labels.yaml file that it uses to sync github labels across repos in the Open Services Group 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, with a single commit, that:
    • updates labels.yaml with the new label(s)
    • runs label_sync (to regenerate the label descriptions and associated CSS)
  • After the PR is merged, a prow job is responsible for syncing labels

You can run label_sync in a container using:

podman run --rm -v ./:/community:z \
       gcr.io/k8s-prow/label_sync:latest \
       --action docs \
       --config /community/labels.yaml \
       --docs-template /community/labels.md.tmpl \
       --docs-output /community/labels.md

Labels that apply to all repos, for both issues and PRs

Name Description Added By Prow Plugin
committee/steering Denotes an issue or PR intended to be handled by the steering committee. anyone label
kind/bug Categorizes issue or PR as related to a bug.

This was previously bug,		 anyone label
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. anyone label
kind/demo This is an Issue or PR someone want to give a demo or request a demo. human label
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. 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.

This was previously enhancement, kind/enhancement,		 anyone label
kind/question Categorizes issue or PR as a support question.

This was previously close/support, question, triage/support,		 humans
lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.

This was previously active,		 anyone lifecycle
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 stale and will be auto-closed. anyone lifecycle
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

This was previously stale,		 anyone lifecycle
priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. anyone label
priority/backlog Higher priority than priority/awaiting-more-evidence. anyone label
priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. anyone label
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. anyone label
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. anyone label
sig/community-experience Denotes an issue or PR relevant to SIG Community Experience. anyone label
sig/data-science Denotes an issue or PR relevant to SIG Data Science. anyone label
sig/services Denotes an issue or PR relevant to SIG Services. anyone label
triage/duplicate Indicates an issue is a duplicate of other open issue.

This was previously close/duplicate, duplicate,		 humans
triage/needs-information Indicates an issue needs more information in order to work on it.

This was previously close/needs-information,		 humans
triage/not-reproducible Indicates an issue can not be reproduced as described.

This was previously close/not-reproducible,		 humans
triage/unresolved Indicates an issue that can not or will not be resolved.

This was previously close/unresolved, invalid, wontfix,		 humans
wg/byon-build-pipelines Categorizes an issue or PR as relevant to WG BYON Build Pipelines. anyone label
wg/devsecops Categorizes an issue or PR as relevant to WG DevSecOps anyone label
¯\_(ツ)_/¯ ¯\_(ツ)_/¯ humans shrug

Labels that apply to all repos, only for issues

Name Description Added By Prow Plugin
tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open.

This was previously merge-blocker,		 humans

Labels that apply to all repos, only for PRs

Name Description Added By Prow Plugin
approved Indicates a PR has been approved by an approver from all required OWNERS files. approvers approve
do-not-merge/blocked-paths Indicates that a PR should not merge because it touches files in blocked paths. prow blockade
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. anyone hold
do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. prow verify-owners
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. prow wip
hacktoberfest-accepted PR that has been accepted for hacktoberfest! humans label
lgtm Indicates that a PR is ready to be merged. reviewers or members lgtm
needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. prow trigger
needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. prow needs-rebase
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
tide/merge-method-merge Denotes a PR that should use a standard merge by tide when it merges. humans
tide/merge-method-rebase Denotes a PR that should be rebased by tide when it merges. humans
tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

This was previously tide/squash,		 humans

Labels that apply to open-services-group/community, for both issues and PRs

Name Description Added By Prow Plugin
area/communication Issues or PRs related to Communication label
area/governance Issues or PRs related to Org Governance label
area/metrics Issues or PRs related to Metrics label

Labels that apply to open-services-group/okr, for both issues and PRs

Name Description Added By Prow Plugin
area/aiops all Key Results belonging to the AIOps endeavor

This was previously aiops,		 label
area/odh-et all Key Results belonging to the ODH ET endeavor

This was previously odh-et,		 label
area/operate-first all Key Results belonging to the Operate First initiative

This was previously operate-first,		 label
area/project-thoth all Key Results belonging to Project Thoth label