Labels
Prioritized labels 0
Drag to reorder prioritized labels and change their relative priority.
Labels 3,888
-
approvalsGitLab.orgIssues related to the Merge Request approvals feature: http://doc.gitlab.com/ee/workflow/merge_request_approvals.html
-
appsec-flow-mr-reviewhelpfulGitLab.orgUse if AppSec's Security MR Reviewer produced a helpful review
-
appsec-flow-mr-reviewmixed-helpfulGitLab.orgUse if AppSec's Security MR Reviewer produced a review with valid findings as well as invalid findings
-
appsec-flow-mr-reviewnon-security-helpfulGitLab.orgUse if AppSec's Security MR Reviewer produced valid but not security related findings
-
appsec-flow-mr-reviewunhelpfulGitLab.orgUse if AppSec's Security MR Reviewer produced an unhelpful review
-
appsec-kpivulnerability-introducedGitLab.orgA label applied to Merge Requests that were later identified as having introduced a vulnerability during a security release. This label is used for tracking review coverage metrics and should be applied retroactively to the original Merge Request when a vulnerability is discovered. The purpose of this label is to help measure the Application Security team's effectiveness in preventing vulnerabilities through code review by tracking which vulnerability-introducing changes went through security review gitlab-com/content-sites/handbook!11439
-
appsec-kpivulnerability-preventedGitLab.orgA label applied to Merge Requests in which a vulnerability was identified and prevented going into production if it was fixed before being merged. This label is used for tracking review coverage metrics. The purpose of this label is to help measure the Application Security team's effectiveness in identified vulnerabilities through code review.
-
appsec-sast-pingresolvedGitLab.orgThis label is applied by an AppSec team member when all findings from AppSec's SAST rules have been reviewed. See https://gitlab.com/gitlab-com/gl-security/appsec/sast-custom-rules
-
appsec-sast-pingunresolvedGitLab.orgThis label is applied automatically when AppSec's SAST rules are flagged on a merge request. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsec-sastcommentedGitLab.orgAdded when automation has detected a SAST violation of GitLab's AppSec team's rules. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsec-sasthelpfulGitLab.orgAdd this label when AppSec's SAST rules were helpful, informative, and/or not unhelpful. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsec-sastunhelpfulGitLab.orgApply this label if AppSec's SAST rules were unhelpful and/or incorrect. See https://gitlab.com/gitlab-com/gl-security/product-security/appsec/sast-custom-rules
-
appsecSecurity Release retroGitLab.orgDenotes issues used for the security release process retrospective in the Application Security team