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
-
tw-leadverifyGitLab.orgItems that are driven by or require input from the Verify Technical Writing stage lead https://handbook.gitlab.com/handbook/product/ux/technical-writing/#stage-leads.
-
tw-styleGitLab.orgRelated to style standards for documentation, UI text (per Pajamas Content guide), or the Release Post.
-
tw-testingGitLab.orgRelated to tools, process, standards for doc/UI/Release Post content testing, including linting. Also use more-specific labels like ~vale or ~markdownlint, if applicable. Typically involving the Technical Writing Test Automation Committee.
-
tw-weight1GitLab.org(optional) Technical Writing team member's effort, similar to fixing a single misspelling or adding a punctuation
-
tw-weight13GitLab.org(optional) Technical Writing team member's effort, similar to creating an entirely new page for a feature or process
-
tw-weight3GitLab.org(optional) Technical Writing team member's effort, similar to developing or revising a few sentences
-
tw-weight5GitLab.org(optional) Technical Writing team member's effort, similar to developing or revising a section of content
-
tw-weight8GitLab.org(optional) Technical Writing team member's effort, similar to revising a full page of provided content, or developing a half page
-
twtriagedGitLab.orgThe Technical Writing effort for this has been identified, and no additional reminders are required from the bot.
-
typebugGitLab.orgIssues that report undesirable or incorrect behavior. See https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
typefeatureGitLab.orgAny issue/MR that contains work to support the implementation of a feature and/or results in an improvement in the user experience. Read more at https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
typeignoreGitLab.orgWhen using this type, the issue will be excluded from cross functional planning metrics. This is used for meta, planning, issues.
- Lock on merge
- Issues
- Merge requests
-
typemaintenanceGitLab.orgUpkeeping efforts and catch-up corrective improvements that are not Feature nor Bugs. Read more at https://handbook.gitlab.com/handbook/product/groups/product-analysis/engineering/metrics/#work-type-classification
- Lock on merge
- Issues
- Merge requests
-
unplanned-upgrade-stopGitLab.orgThe label is for upgrade bugs which resulted in retroactively adding required upgrade stop to the Upgrade Path. Also applied to the relevant Root Cause Analysis issues for such upgrade bugs. https://handbook.gitlab.com/handbook/engineering/unplanned-upgrade-stop/
-
upcoming security releaseGitLab.orgGitLab security releases. This label should only be added for (critical) security root/meta issues. Do not add this label to individual security issues and/or merge requests.