Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 2,939
-
release post itemdeprecationGitLab.orgGenerates a 'deprecation' release post item for this issue in the www-gitlab-com project
-
release post itemprimaryGitLab.orgGenerates a 'primary' release post item for this issue in the www-gitlab-com project
-
release post itemremovalGitLab.orgGenerates a 'removal' release post item for this issue in the www-gitlab-com project
-
release post itemsecondaryGitLab.orgGenerates a 'secondary' release post item for this issue in the www-gitlab-com project
-
release post itemtopGitLab.orgGenerates a 'top' release post item for this issue in the www-gitlab-com project
-
release-blockerGitLab.orgAn issue or a task blocking a release, either auto_deploy or customer packages
-
releasedcandidateGitLab.orgAs a merge request is included in self-managed releases, it will receive the released::candidate label when the release candidate it is included in is deployed to pre.gitlab.com. https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-2
-
releasedpublishedGitLab.orgA merge request will receive the released::published label when included in a packaged release, such as 13.6.0 or 13.5.2, and deployed to release.gitlab.net for both automated and manual testing. https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-2
-
replacing-gerritGitLab.orgChanges requested by customers seeking to replace Gerrit (see also #replacing-gerrit on GitLab internal Slack)
-
reply by emailGitLab.orgIssues related to the Reply by email feature: https://docs.gitlab.com/ee/administration/reply_by_email.html