Other labels
direction
GitLab.org
Issues for important features that are on our roadmap: https://about.gitlab.com/direction/
discoto
GitLab.org
Causes declared discussion points and topics to be auto-summarized. https://gitlab.com/gitlab-org/secure/pocs/discussion-automation
discoto-beta
GitLab.org
Causes declared discussion points and topics to be auto-summarized BY THE BETA BUILD OF https://gitlab.com/gitlab-org/secure/pocs/discussion-automation
docs-archives
GitLab.org
Issues, merge requests, and epics related to the docs archives https://gitlab.com/gitlab-org/gitlab-docs-archives
docs-channel
GitLab.org
A Technical Writer has picked up this item from the docs or tw-team Slack channels, or from roulette, AND the item is outside of their assigned groups.
docs-comments
GitLab.org
Apply this label only on issues/MRs that reply to a community comment in docs.gitlab.com
docs-discussion
GitLab.org
An idea or proposal for documentation content. For documentation site features, use https://gitlab.com/gitlab-com/gitlab-docs/issues
docs-linting
GitLab.org
Related to docs linting (markdownlint, Vale) https://docs.gitlab.com/ee/development/documentation/testing.html#local-linters
docs-missing
GitLab.org
Issues with missing documentation. Technical Writing team to follow up with Development team.
docs-only
GitLab.org
Issues and MRs that only require a documentation change, to differentiate from those coupled with a feature change
docs-sitediscussion
GitLab.org
Ongoing discussions and proposals related to the docs site (not ready for development yet)
docs-siteready-for-development
GitLab.org
Issues, MRs, Epics for docs.gitlab.com ready for development by engs and UXers
docs-technical-debt
GitLab.org
A follow-up issue/MR for additional documentation work from merged MRs. This can occur when more work is required after a technical writer review, or if a technical writer review didn’t occur.
docs-weight1
GitLab.org
(Trivial) Tiny change, such as fixing a single misspelling or grammatical mistake.
Prioritized