Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
sectiondata-scienceGitLab.orgIssues related to the Data Science section including ModelOps and Anti-Abuse Stages
-
sectionplatformsGitLab.orgPlatform Infrastructure section https://about.gitlab.com/direction/platforms/ (per gitlab-com/www-gitlab-com!86383)
-
secure bulk changesGitLab.orgItems related to managing secure stage configuration, policy or rules to more than one project at a time
-
secure experienceGitLab.orgEngineering work that cuts across the entire secure stage and how we strategically think about the BE/FE experience in a holistic way.
-
secure merge request approvalGitLab.orgAnything related to the vulnerability-check rule, aka security gates or security approvals, in the MR.
-
secure offline scanningGitLab.orgIssues related to enabling secure scans to run in offline self-managed instances also called air-gap or limited connectivity
-
secure settingsGitLab.orgCustomer ability to edit Settings, Configuration, and Policy enforcement related to Secure stage categories and features.
-
secure:generic report schemaGitLab.orgIssues that could affect or benefit from the Generic Report Schema detailed at &4466
-
secure:refinement-backendGitLab.orgIssues that need engineering refinement from a given Secure backend team (please use in conjunction with group label).
-
secure:refinement-frontendGitLab.orgIssues that need engineering refinement from the Secure Frontend team.
-
securityGitLab.orgIssues related to the security of GitLab or its dependencies. Please report vulnerabilities responsibly per https://about.gitlab.com/security/disclosure/
Prioritized