Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,576
-
Pipeline Abuse Prevention PVS part of the Anti-Abuse group of the Anti-abuse Stage
-
Issues related to CI pipeline statistics and dashboards.
-
Pipeline failure issue that needs investigation.
-
Pipeline failure that is under investigation
-
Issues related to the execution of pipeline jobs, including DAG, child pipelines, and matrix build jobs.
-
Issues related to visualization of CI pipelines, including pipeline graphs, pipeline dependencies for triggers, cross-project pipelines, and child/parent pipelines.
-
Set this label on "master fixing" or urgent revert MRs to skip Review Apps and QA related jobs
-
Tier 1 pipelines are run when a merge request has no approvals. See gitlab-org/quality/engineering-productivity&58 for more info.
-
Tier 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.
-
Tier 3 pipelines are run when a merge request has all the approvals it needs. See gitlab-org/quality/engineering-productivity&58 for more info.
-
Force 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
-
Indicates 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
-
Associated 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/
-
Indicates that associated merge request pipelines will be forced to run all the jest jobs to regardless of the changes
-
Indicates that associated merge request pipelines will be forced to run all the RSpec jobs to regardless of the changes
-
Indicates that associated merge request pipeline jobs would run in the context of the `gitlab-org/gitlab-foss` project
-
Indicates 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`