You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/code-security/secure-coding/about-code-scanning.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ versions:
12
12
topics:
13
13
- security
14
14
---
15
+
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
15
16
16
17
{% data reusables.code-scanning.beta %}
17
18
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
@@ -59,7 +60,6 @@ You can view and contribute to the queries for {% data variables.product.prodnam
59
60
60
61
### Further reading
61
62
62
-
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
63
-
- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"{% endif %}
63
+
- "[About securing your repository](/github/administering-a-repository/about-securing-your-repository)"
64
64
-[{% data variables.product.prodname_security %}](https://securitylab.github.com/)
65
65
-[OASIS Static Analysis Results Interchange Format (SARIF) TC](https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sarif) on the OASIS Committee website
Copy file name to clipboardExpand all lines: content/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository.md
+3-23Lines changed: 3 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Managing code scanning alerts for your repository
3
3
shortTitle: Managing alerts
4
-
intro: 'From the security view, you can view, fix, {% if currentVersion == "enterprise-server@2.22" %}or close{% else %}dismiss, or delete{% endif %} alerts for potential vulnerabilities or errors in your project''s code.'
4
+
intro: 'From the security view, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your project''s code.'
5
5
product: '{% data reusables.gated-features.code-scanning %}'
6
6
permissions: 'If you have write permission to a repository you can manage {% data variables.product.prodname_code_scanning %} alerts for that repository.'
7
7
versions:
@@ -15,6 +15,7 @@ redirect_from:
15
15
topics:
16
16
- security
17
17
---
18
+
<!--For this article in earlier GHES versions, see /content/github/finding-security-vulnerabilities-and-errors-in-your-code-->
18
19
19
20
{% data reusables.code-scanning.beta %}
20
21
@@ -63,7 +64,7 @@ You need write permission to view a summary of all the alerts for a repository o
63
64
64
65
Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has {% data variables.product.prodname_code_scanning %} scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger {% data variables.product.prodname_code_scanning %} analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
65
66
66
-
If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have {% if currentVersion == "enterprise-server@2.22" %}closed{% else %}dismissed{% endif %}.
67
+
If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking **Closed**. For more information, see "[Viewing the alerts for a repository](#viewing-the-alerts-for-a-repository)." The "Closed" list shows fixed alerts and alerts that users have dismissed.
67
68
68
69
Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.
69
70
@@ -73,14 +74,6 @@ Alerts may be fixed in one branch but not in another. You can use the "Branch" d
73
74
74
75
{% endif %}
75
76
76
-
{% if currentVersion == "enterprise-server@2.22" %}
77
-
78
-
### Closing an alert
79
-
80
-
Closing an alert is a way to resolve an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %}
81
-
82
-
{% else %}
83
-
84
77
### Dismissing or deleting alerts
85
78
86
79
There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, if you have admin permissions for the repository, you can delete alerts. Deleting alerts is useful in situations where you have set up a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have configured {% data variables.product.prodname_codeql %} analysis with a larger set of queries than you want to continue using, and you've then removed some queries from the tool. In both cases, deleting alerts allows you to clean up your {% data variables.product.prodname_code_scanning %} results. You can delete alerts from the summary list within the **Security** tab.
@@ -104,20 +97,9 @@ When you delete an alert:
104
97
105
98
To dismiss or delete alerts:
106
99
107
-
{% endif %}
108
-
109
100
{% data reusables.repositories.navigate-to-repo %}
110
101
{% data reusables.repositories.sidebar-security %}
111
102
{% data reusables.repositories.sidebar-code-scanning-alerts %}
112
-
{% if currentVersion == "enterprise-server@2.22" %}
113
-
{% data reusables.code-scanning.click-alert-in-list %}
114
-
1. Select the **Close** drop-down menu and click a reason for closing the alert.
115
-
116
-
117
-
{% data reusables.code-scanning.false-positive-fix-codeql %}
118
-
119
-
{% else %}
120
-
121
103
1. If you have admin permissions for the repository, and you want to delete alerts for this {% data variables.product.prodname_code_scanning %} tool, select some or all of the check boxes and click **Delete**.
If a project has multiple alerts that you want to dismiss for the same reason, you can bulk dismiss them from the summary of alerts. Typically, you'll want to filter the list and then dismiss all of the matching alerts. For example, you might want to dismiss all of the current alerts in the project that have been tagged for a particular Common Weakness Enumeration (CWE) vulnerability.
151
133
152
-
{% endif %}
153
-
154
134
### Further reading
155
135
156
136
- "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)"
0 commit comments