Labels
Prioritized labels 9
Drag to reorder prioritized labels and change their relative priority.
-
frontendGitLab.orgIssues for the Frontend team. Covers everything related to the way GitLab behaves (and, to an extent, looks) inside your browser.
-
golangGitLab.orgIssues for Ruby teams that require some knowledge of Go, because they may require changes in Gitaly, Workhorse, etc
-
workflowready for developmentGitLab.orgIssue has been broken down and prioritized by PM for development https://handbook.gitlab.com/handbook/product-development-flow/#description-4
-
workflowin devGitLab.orgIssues that are actively being worked on by a developer https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
workflowin reviewGitLab.orgIssues that are undergoing code review by the development team and/or undergoing design review by the UX team https://handbook.gitlab.com/handbook/product-development-flow/#description-5
-
workflowverificationGitLab.orgEverything has been merged, waiting for verification after a deploy https://handbook.gitlab.com/handbook/product-development-flow/#description-5
Labels 3,529
-
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