Labels
Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels 3,860
-
Things that affect security of GitLab.com, self-managed instances, or GitLab corporation that need the attention of the Security Department
-
Indicates the issue is a request from the Security Department
-
Issue or Merge Request awarded! See https://about.gitlab.com/handbook/engineering/security/security-awards-program.html
-
Issue or Merge Request nominated for a security award. See https://about.gitlab.com/handbook/engineering/security/security-awards-program.html
-
In relation with the Security Champions Program - https://about.gitlab.com/handbook/engineering/security/security-champions-program.html
-
Security issue is missing a group:: label (automated label)
-
Security issue has been escalated (automated label)
-
Subscribes the issue for automatic notifications related to security releases. This label is meant for use on Security Implementation Issues on the security mirror projects.
-
Security issue needs a milestone with (future) dates (automated label)
-
Security issues is missing severity or priority label (automated label)
-
(Not yet implemented) Security implementation issues with this label will be considered for the next scheduled security release.
-
Security issue to be triaged by the AppSec team (automated label)
-
Instructs @gitlab-securitybot to skip the automation on this specific issue or MR
-
For items that are primarily related to self-managed instances
-
Label applied to merge requests that were approved and or merged by automation. Used for some Renovate MRs, among other things.