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:run-e2e-omnibus-onceGitLab.orgAutomation-only label: no need to apply it manually. Indicates that the next merged results pipeline should run E2E Omnibus tests once (if applicable for the type of changes).
-
pipeline:run-praefect-with-dbGitLab.orgRun tests with Praefect using a PostgreSQL database instead of an in-memory election strategy
-
pipeline:run-search-testsGitLab.orgIndicates that associated merge request pipelines will run all the RSpec jobs for Elasticsearch and OpenSearch
-
pipeline:run-single-dbGitLab.orgIndicates that associated merge request pipelines will run jobs with a single database
-
pipeline:single-db-sec-connectionGitLab.orgIndicates that associated merge request pipelines will run jobs where `gitlab_sec` tables use a different DB connection
-
pipeline:skip-undercoverageGitLab.orgIndicates that the undercoverage job for the merge request will be allowed to fail
-
pipeline:too-oldGitLab.orgThis is an automatically-applied label when the latest pipeline on a merged MR was creating too long ago at the time of merging.
-
pipeline:update-cacheGitLab.orgIndicates that associated merge request pipelines will be run jobs to force caches to be updated
-
plantriageGitLab.orgAn issue that is not assigned an epic, milestone, or contains not enough information. It requires more triaging to decide its fate.
-
planning priorityGitLab.orgIssues which are particularly important to be released in the specified milestone. This should only be set by the responsible PM.
-
planningrefinementGitLab.orgAn issue which has been validated and breakdown started, but requires further refinement before development can begin. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382
-
planningto-doGitLab.orgAn issue which has been validated and ready for planning/design/development. This label is being used as part of an experiment and should not be manually added/removed. See gitlab-org/developer-relations/contributor-success/team-task#382
-
platform-specificGitLab.orgOutlier that relates to a single distribution, platform, or architecture (eg Debian/AWS/ARM/)
-
platform-to-createGitLab.orgIssues migrated from Platform label to Create label Ref: gitlab-org/quality/triage-ops#59