Skip to content

Commit e8954a2

Browse files
guntripgithub-actionsethanpalm
authored
[2022-03-03]: Reopen dismissed Dependabot alerts (GA) (github#25659)
* Add feature, screenshot, article changes * Optimize images * empty to try and trigger deploy * add ghae versioning * add screenshot, fix drop-down * Optimize images Co-authored-by: github-actions <[email protected]> Co-authored-by: Ethan Palm <[email protected]>
1 parent eef70d0 commit e8954a2

File tree

5 files changed

+23
-1
lines changed

5 files changed

+23
-1
lines changed
18.7 KB
Loading
29 KB
Loading
43.1 KB
Loading

content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Each {% data variables.product.prodname_dependabot %} alert has a unique numeric
5757
1. Optionally, if there isn't already a {% data variables.product.prodname_dependabot_security_updates %} update for the alert, to create a pull request to resolve the vulnerability, click **Create {% data variables.product.prodname_dependabot %} security update**.
5858
![Create {% data variables.product.prodname_dependabot %} security update button](/assets/images/help/repository/create-dependabot-security-update-button-ungrouped.png)
5959
1. When you're ready to update your dependency and resolve the vulnerability, merge the pull request. Each pull request raised by {% data variables.product.prodname_dependabot %} includes information on commands you can use to control {% data variables.product.prodname_dependabot %}. For more information, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
60-
1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" drop-down, and click a reason for dismissing the alert.
60+
1. Optionally, if the alert is being fixed, if it's incorrect, or located in unused code, select the "Dismiss" dropdown, and click a reason for dismissing the alert.{% if reopen-dependabot-alerts %} Unfixed dismissed alerts can be reopened later.{% endif %}
6161
![Choosing reason for dismissing the alert via the "Dismiss" drop-down](/assets/images/help/repository/dependabot-alert-dismiss-drop-down-ungrouped.png)
6262

6363
{% elsif ghes = 3.3 %}
@@ -94,6 +94,22 @@ Each {% data variables.product.prodname_dependabot %} alert has a unique numeric
9494
![Dismiss security banner](/assets/images/enterprise/3.0/dependabot-alert-dismiss.png)
9595
{% endif %}
9696

97+
{% if reopen-dependabot-alerts %}
98+
99+
## Viewing and updating closed alerts
100+
101+
{% data reusables.repositories.navigate-to-repo %}
102+
{% data reusables.repositories.sidebar-security %}
103+
{% data reusables.repositories.sidebar-dependabot-alerts %}
104+
1. To just view closed alerts, click **Closed**.
105+
![Screenshot showing the "Closed" option](/assets/images/help/repository/dependabot-alerts-closed.png)
106+
1. Click the alert that you would like to view or update.
107+
![Screenshot showing a highlighted dependabot alert](/assets/images/help/repository/dependabot-alerts-select-closed-alert.png)
108+
2. Optionally, if the alert was dismissed and you wish to reopen it, click **Reopen**.
109+
![Screenshot showing the "Reopen" button](/assets/images/help/repository/reopen-dismissed-alert.png)
110+
111+
{% endif %}
112+
97113
## Further reading
98114

99115
- "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# Reference 5861
2+
versions:
3+
fpt: '*'
4+
ghec: '*'
5+
ghes: '>3.4'
6+
ghae: 'issue-5861'

0 commit comments

Comments
 (0)