- Intro
- Labels that apply to all repos, for both issues and PRs
- Labels that apply to all repos, only for issues
- Labels that apply to all repos, only for PRs
- Labels that apply to operate-first/peribolos-as-a-service, for both issues and PRs
- Labels that apply to operate-first/probot-extensions, for both issues and PRs
- Labels that apply to operate-first/service-catalog, for both issues and PRs
This 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 Operate First GitHub org
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.
- Add automation that consumes/produces the label
- Open a PR, with a single commit, that:
- updates labels.yaml with the new label(s)
- After the PR is merged, a CronJob is responsible for syncing labels
| Name | Description | Added By | Prow Plugin |
|---|---|---|---|
area/community |
Indicates an issue/PR is related to the overall community. | anyone | label |
area/contributor |
Indicates an issue/PR is related to a project platform contributor. | anyone | label |
area/hardware |
Indicates an issue/PR is related to hardware. | anyone | label |
area/monitoring |
Indicates an issue/PR is related to monitoring. | anyone | label |
area/networking |
Indicates an issue/PR is related to networking. | anyone | label |
area/security |
Indicates an issue/PR is related to security. | anyone | label |
area/service/acm |
Indicates an issue/PR is related to ACM. | anyone | label |
area/service/argocd |
Indicates an issue/PR is related to ArgoCD. | anyone | label |
area/service/grafana |
Indicates an issue/PR is related to Grafana. | anyone | label |
area/service/ocs |
Indicates an issue/PR is related to Openshift Container Storage. | anyone | label |
area/service/odh |
Indicates an issue/PR is related to Open Data Hub. | anyone | label |
area/service/uwm |
Indicates an issue/PR is related to user workload monitoring. | anyone | label |
area/storage |
Indicates an issue/PR is related to storage. | anyone | label |
area/user |
Indicates an issue/PR is related to a project platform user. | anyone | label |
kind/academic-administrator |
Connects an issue/PR with a particular user persona. | anyone | label |
kind/academic-researcher |
Connects an issue/PR with a particular user persona. | anyone | label |
kind/bug |
Categorizes issue or PR as related to a bug. This was previously bug, |
anyone | label |
kind/business-owner |
Connects an issue/PR with a particular user persona. | anyone | label |
kind/cleanup |
Categorizes issue or PR as related to cleaning up code, process, or technical debt. | anyone | label |
kind/data-engineer |
Connects an issue/PR with a particular user persona. | anyone | label |
kind/data-scientist |
Connects an issue/PR with a particular user persona. | anyone | 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. This was previously docs, documentation, |
anyone | label |
kind/experience |
Indicates an issue/PR is related to human interaction and experience. | anyone | label |
kind/feature |
Categorizes issue or PR as related to a new feature. This was previously enhancement, kind/enhancement, |
anyone | label |
kind/general-public |
Connects an issue/PR with a particular user persona. | anyone | label |
kind/governance |
Indicates an issue/PR is related to governance. | anyone | label |
kind/handbook |
Indicates an issue/PR is related to a handbook. | anyone | label |
kind/marketing |
Indicates an issue/PR is related to marketing. | anyone | label |
kind/metrics |
Indicates an issue/PR is related to metrics. | anyone | label |
kind/news |
Indicates an issue/PR is related to project news and outreach. | anyone | label |
kind/onboarding |
Indicates an issue/PR is related to onboarding. | anyone | label |
kind/open-source-developer |
Connects an issue/PR with a particular user persona. | anyone | label |
kind/question |
Categorizes issue or PR as a support question. This was previously close/support, question, triage/support, |
humans | |
kind/sigs |
Indicates an issue/PR is related to Special Interest Groups (SIGs) | anyone | label |
kind/undergrad-student |
Connects an issue/PR with a particular user persona. | anyone | label |
kind/website |
Indicates an issue/PR is related to project web presence. | anyone | label |
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 |
Categorizes an issue or PR as relevant to SIG Community | anyone | label |
sig/cyborgs |
Categorizes an issue or PR as relevant to SIG Cyborgs and Bots. | anyone | label |
sig/devops |
Categorizes an issue or PR as relevant to SIG DevOps. | anyone | label |
sig/docs |
Categorizes an issue or PR as relevant to SIG Docs. This was previously sig/documentation, |
anyone | label |
sig/operations |
Categorizes an issue or PR as relevant to SIG Operations | anyone | label |
sig/pipelines |
Categorizes an issue or PR as relevant to SIG Pipelines (CI/CD) This was previously sig/build, |
anyone | label |
sig/sre |
Categorizes an issue or PR as relevant to SIG SRE | anyone | label |
triage/accepted |
Indicates an issue or PR is ready to be actively worked on. | org members | 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 | |
user/experience |
Indicates an issue/PR is user experience (UX). | anyone | label |
users/documentation |
Indicates an issue/PR is related to end-user documentation. | anyone | label |
¯\_(ツ)_/¯ |
¯\_(ツ)_/¯ | humans | shrug |
| Name | Description | Added By | Prow Plugin |
|---|---|---|---|
good first issue |
Good for newcomers | anyone | label |
kind/cluster-upgrade |
Issues about upcoming cluster upgrades. | anyone | label |
kind/task |
Issues that clearly identify an actionable task, scoped appropriately. | anyone | label |
kind/user-story |
Categorizes an issue as capturing a user story | anyone | label |
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 |
| 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 |
| Name | Description | Added By | Prow Plugin |
|---|---|---|---|
kind/promote |
Automated promotion of deployment between environments | humans | |
kind/release |
Automated release trigger | humans | |
released |
Marks issues as released | anyone |
| Name | Description | Added By | Prow Plugin |
|---|---|---|---|
kind/release |
Automated release trigger | humans | |
released |
Marks issues as released | anyone |
| Name | Description | Added By | Prow Plugin |
|---|---|---|---|
kind/plugin |
Related to a backstage plugin in the service catalog | humans | |
kind/system-definition |
Related to creating a system inside the service catalog | humans |