Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
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.
-
pipeline:expect-group-changesGitLab.org / FrontendUse this to allow path/group ownership changes in the `compare groups` job for projects like the Pajamas Adoption Scanner.
-
pipeline:expediteGitLab.orgSet this label on "master fixing" or urgent revert MRs to skip Review Apps and QA related jobs
-
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:ignore-master-statusGitLab.orgSkip the automatic canceling behavior when a pipeline is likely going to fail. With this label added, MR pipelines will run until the end. Owned by Engineering Productivity
-
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`
-
pipeline:run-clusterwide-dbGitLab.orgSetups databases with a new connection `main_clusterwide`, but pointing to the same database as `main`, and run RSpec jobs with this DB configuration.
-
pipeline:run-praefect-with-dbGitLab.orgRun tests with Praefect using a PostgreSQL database instead of an in-memory election strategy
Prioritized