* Changed 'people' to 'accounts'
Adding some precision: Changed 'People with write permission to a repository can manage' to 'Accounts with write permission to a repository can manage"
People don't have permission; accounts have permission.
* edits for clarity
* clarity
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository.md
Co-authored-by: hubwriter <54933897+hubwriter@users.noreply.github.com>
Co-authored-by: hubwriter <54933897+hubwriter@users.noreply.github.com>
* Use conditioning to revert dismiss/delete alert changes on GHES
* Add new dotcom version text that is also good for GHES
* Reinstate original subheading for GHES 2.22
* Use conditioning to revert dismiss/delete alert changes on GHES
* Add new dotcom version text that is also good for GHES
* Reinstate original subheading for GHES 2.22
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>
* Updates for delete and dismiss alerts
* Add back the text for the now-deleted reusable
* Make s/shots relevant to the PR context of the text
* Make review comment changes
* More review comments attended to
* Add back changes from prior to purge
* Manually fix some invalid Liquid
* Updoot render-content
* Improve test messages to show correct output
* Run el scripto
* Pass the remaining test
