Labels
Prioritized labels 25
Drag to reorder prioritized labels and change their relative priority.
-
Category:ServerlessGitLab.orgAll issues and MRs related to the Serverless category within devops::configure. https://about.gitlab.com/direction/configure/serverless/
-
dockerfileGitLab.org / GitLab Docs DEPRECATEDRelated to the dockerfiles present in the gitlab-docs project
-
Category:Chaos EngineeringGitLab.orgIssues related to chaos engineering (part of ~devops:configure stage)
-
devopsconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use devops::deploy now. Issues for the Configure stage of the DevOps lifecycle (e.g. Auto DevOps , Kubernetes Configuration, ChatOps, Serverless, PaaS)
-
Category:Infrastructure as CodeGitLab.orgAll issues and MRs related to the Infrastructure as Code category within devops::configure. https://about.gitlab.com/direction/configure
-
[deprecated] Accepting merge requestsGitLab.org[deprecated] Please use "Seeking community contributions" instead. gitlab-org/developer-relations/contributor-success/team-task#77
-
Category:Cluster MonitoringGitLab.orgIssues belonging to the Monitor stage Health group for product category Cluster Monitoring
-
Category:Auto DevOpsGitLab.orgIssues for Auto DevOps, part of the Configure stage of the DevOps lifecycle
-
Category:Code QualityGitLab.orgAll issues and MRs related to the Code Quality category. See https://about.gitlab.com/direction/secure/static-analysis/code-quality/
-
Category:Container RegistryGitLab.orgCategory label - Features that apply to management container registries
-
groupconfigure [DEPRECATED]GitLab.org[DEPRECATED] should use group::environments. Issues belonging to the Configure group of the Configure stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#configure-group
-
Category:Continuous IntegrationGitLab.orgAll issues and MRs related to the continuous integration category within devops:verify https://about.gitlab.com/direction/verify/continuous_integration
-
infrastructure configurationGitLab.orgIssues for Infrastructure Configuration, part of the Configure stage of the DevOps lifecycle
-
Category:Cluster Cost OptimizationGitLab.orgIssues related to the "cluster cost optimization" category of the configure stage. See &503
-
Category:Cloud Native InstallationGitLab.org
-
development guidelinesGitLab.orgChanges or updates to the development guidelines in the /development directory in the GitLab documentation. (Info: https://docs.gitlab.com/ee/development/)
-
groupsource codeGitLab.orgIssues belonging to the Source Code group of the Create stage of the DevOps lifecycle. See https://about.gitlab.com/handbook/product/categories/#source-code-group
-
grouprunner coreGitLab.orgIssues belonging to the Runner group of the Verify stage of the DevOps lifecycle.
-
Category:Kubernetes ManagementGitLab.orgRelating the `Kubernetes Management` category within the configure stage
Labels 3,627
-
pipeline abuse preventionGitLab.orgPipeline Abuse Prevention PVS part of the Anti-Abuse group of the Anti-abuse Stage
-
pipeline processingGitLab.orgIssues related to the execution of pipeline jobs, including DAG, child pipelines, and matrix build jobs.
-
pipeline visualizationsGitLab.orgIssues related to visualization of CI pipelines, including pipeline graphs, pipeline dependencies for triggers, cross-project pipelines, and child/parent pipelines.
-
pipelineexpeditedGitLab.orgSet this label on "master fixing" or urgent revert MRs to skip Review Apps and QA related jobs
-
pipelinetier-1GitLab.orgTier 1 pipelines are run when a merge request has no approvals. See gitlab-org/quality/engineering-productivity&58 for more info.
-
pipelinetier-2GitLab.orgTier 2 pipelines are run when a merge request has at at least one approval, but still requires more approvals. See gitlab-org/quality/engineering-productivity&58 for more info.
-
pipelinetier-3GitLab.orgTier 3 pipelines are run when a merge request has all the approvals it needs. See gitlab-org/quality/engineering-productivity&58 for more info.
-
pipeline:force-run-as-if-jhGitLab.orgForce as-if-jh pipeline to run even when it's disabled by $CI_AS_IF_JH_ENABLED. See ~"pipeline:run-as-if-jh" for details
-
pipeline:mr-approvedGitLab.orgIndicates that associated merge request pipelines will be forced to run non-minimal sets of RSpec and Jest tests. More info at https://docs.gitlab.com/ee/development/pipelines/index.html#rspec-minimal-jobs and https://docs.gitlab.com/ee/development/pipelines/index.html#jest-minimal-jobs
-
pipeline:run-CS-evaluationGitLab.orgAssociated merge request pipelines will include a multi-project pipeline to evaluate Code Suggestions via https://gitlab.com/gitlab-com/create-stage/code-creation/code-suggestion-scenarios/
-
pipeline:run-all-jestGitLab.orgIndicates that associated merge request pipelines will be forced to run all the jest jobs to regardless of the changes
-
pipeline:run-all-rspecGitLab.orgIndicates that associated merge request pipelines will be forced to run all the RSpec jobs to regardless of the changes
-
pipeline:run-as-if-fossGitLab.orgIndicates that associated merge request pipeline jobs would run in the context of the `gitlab-org/gitlab-foss` project
-
pipeline:run-as-if-jhGitLab.orgIndicates that associated merge request pipeline will trigger a cross project downstream pipeline in GitLab JH validation project. See https://docs.gitlab.com/ee/development/pipelines/#as-if-jh-cross-project-downstream-pipeline Can be disabled by setting $CI_AS_IF_JH_ENABLED to `false`