Skip to content

Latest commit

 

History

History
119 lines (104 loc) · 16.5 KB

labels.md

File metadata and controls

119 lines (104 loc) · 16.5 KB

Thoth Station GitHub Organization Labels

Table of Contents

Intro

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 Thoth Station 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:
  • After the PR is merged, a CronJob is responsible for syncing labels

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

Name Description Added By Prow Plugin
area/adviser Issues or PRs related to Adviser label
area/amun Issues or PRs related to Amun label
area/cyborgs Issues or PRs related to Bots, Apps, Cyborgs, and Kebechet label
area/indicators Issues or PRs related to {meta|performance|security} indicators. label
area/investigator Issues or PRs related to Investigator label
area/knowledge-graph Issues or PRs related to Knowledge Graph label
area/management-api Issues or PRs related to the Management API
area/metrics-exporter Issues or PRs related to the Metrics Exporter
area/predictable-stack Issues or PRs related to the Predictable Stack Pattern label
area/prescriptions Issues or PRs related to Prescriptions label
area/solver Issues or PRs related to Solver label
area/user-api Issues or PRs related to the User API label
bot This Issue or PR is being worked on by a bot human or bot label
deployment_name/ocp4-stage This Issue or PR is related to a specific deployment.

This was previously deployment_name/ocp-stage,
human label
deployment_name/ocp4-test This Issue or PR is related to a specific deployment.

This was previously deployment_name/ocp-test,
human label
deployment_name/prod This Issue or PR is related to a specific deployment.

This was previously deployment_name/zero-prod, deployment_name/moc,
human 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/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps.

This was previously sig/build, sig/cyborgs, sig/devops, sig/pipelines,
anyone label
sig/observability Categorizes an issue or PR as relevant to SIG Observability

This was previously sig/indicators, sig/slo,
anyone label
sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

This was previously area/stack-guidance, sig/investigator, sig/knowledge-graph, sig/solvers, sig/adviser,
anyone label
sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

This was previously sig/docs,
human label
thoth/human-intervention-required This isse/PR requires human intervention! both
thoth/potential-observation This is a potential observation we need to learn from!

This was previously thoth/potential-flake,
humans
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
wg/cre Issues or PRs related to the Custom Runtime Environment (fka Custom Notebook Image) ODH feature.

This was previously wg/cnbi, area/byon,
anyone label
wg/traas Issues or PRs related to the java-prescriptions feature. anyone label
¯\_(ツ)_/¯ ¯\_(ツ)_/¯ humans shrug

Labels that apply to all repos, only for issues

Name Description Added By Prow Plugin
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.

This was previously good-first-issue,
anyone help
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

This was previously help-wanted,
anyone help
thoth/group-programming This issue could be used for group programming, offer or request. humans
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 thoth-station/thoth-application, for both issues and PRs

Name Description Added By Prow Plugin
area/release-eng Issues or PRs related to Release Engineering anyone label