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,629
-
community-bonus200GitLab.orgIf you solve this issue, you'll be assigned a community bonus of 200 points
-
community-bonus300GitLab.orgIf you solve this issue, you'll be assigned a community bonus of 300 points
-
community-bonus500GitLab.orgIf you solve this issue, you'll be assigned a community bonus of 500 points
-
compass-blockerGitLab.orgLabel used to track work related to improving data integrity across gitlab (as it pertains to project Compass). https://about.gitlab.com/direction/product-intelligence/#resolve-data-integrity-concerns
-
competitiveGitLab.orgIssues that are related to competing with another tool or solution identified during Competitive Roadmap Reviews
-
completeunverifiedGitLab.orgAn issue which has been validated, broken down, planned/designed, developed, deployed, but not verified in production. 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
-
completeverifiedGitLab.orgAn issue which has been validated, broken down, planned/designed, developed, deployed, and verified in production. 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
-
complexityhighGitLab.orgIssue with high technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
-
complexitylowGitLab.orgIssue with low technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.
-
complexitymediumGitLab.orgIssue with medium technical complexity. Complexity does not describe the time it will likely require to address the issue, but rather the familiarity required to address it. This label is only intended as a guideline to hint to individuals how involved the issue will likely be.