Skip to content

Commit 6932075

Browse files
Update managing-code-scanning-alerts-for-your-repository.md (#760)
Edited introductory paragraph and step 4 of the section to state that admin permissions are required to delete alerts. Introductory paragraph changed to say, "Alternatively, if you have admin permissions for the repository, you can delete alerts." and step 4 to "If you have admin permissions for the repository, and you want to delete alerts[...]" Co-authored-by: hubwriter <54933897+hubwriter@users.noreply.github.com>
1 parent 0d0e351 commit 6932075

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Alerts may be fixed in one branch but not in another. You can use the "Branch" d
5656

5757
### Dismissing or deleting alerts
5858

59-
There are two ways of closing an alert. You can fix the problem in the code, or you can dismiss the alert. Alternatively, you can delete alerts. Deleting alerts is useful in situations where you have enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% 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.
59+
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 enabled a {% data variables.product.prodname_code_scanning %} tool and then decided to remove it, or where you have enabled {% 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.
6060

6161
Dismissing an alert is a way of closing an alert that you don't think needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} You can dismiss alerts from {% data variables.product.prodname_code_scanning %} annotations in code, or from the summary list within the **Security** tab.
6262

@@ -81,7 +81,7 @@ To dismiss or delete alerts:
8181
{% data reusables.repositories.sidebar-security %}
8282
{% data reusables.repositories.sidebar-code-scanning-alerts %}
8383

84-
1. If 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**.
84+
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**.
8585

8686
![Deleting alerts](/assets/images/help/repository/code-scanning-delete-alerts.png)
8787

0 commit comments

Comments
 (0)