This label describes a broken master scenario with the error "Gitlab is unable to handle this request due to load."

This indicates an issue or merge request can impact JiHu

Epics, issues, and merge requests related to lunr.js search for the Docs site

Epics, issues, and merge requests related to Algolia search for the Docs site

Epics, issues, and merge requests related to Google search for the Docs site

Environements group: In order to keep a manageable backlog of issues we are actively focusing on, we apply this label to the issues that we intend to check regularly, but do not plan any work on them currently.

Issue is in the Environments backlog of work to be done

This is to indicate master broken incidents caused by external dependency issues such as npm registry down, RubyGems.org down, etc.

Label for Plan Stage Feedback Issues

Indicates that Data Team should perform a impact check on the MR

Indicates that there is a impact on Data Warehouse

Indicates that this MR is not impacting Data Warehouse

Issues for the Data Stores stage of the DevOps lifecycle (Application Performance, Database, Global Search, Tenant Scale)

This label is for master broken incidents occured because gitaly is failed to setup. See example: gitlab-org/quality/engineering-productivity/master-broken-incidents#625

This label represents a broken master pipeline caused by failing to pull docker image from the image registry.

[DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)

[DEPRECATED] should use devops::deploy. Issues for the Release stage of the DevOps lifecycle (e.g. CD, Release Automation, Pages, Review apps)

[DEPRECATED] should use group::environments now. Issues belonging to the Release stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#progressive-delivery-group