Skip to content
This repository was archived by the owner on Sep 1, 2022. It is now read-only.

Commit 8482f01

Browse files
committed
remove link to "insights" because it is different on .com vs ghe
1 parent f8441de commit 8482f01

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

responses/02_find-vulnerabilities.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -28,11 +28,11 @@ Use GitHub's security alerts to identify a vulnerable NPM dependency.
2828

2929
### :keyboard: Activity: Identify the suggested version update
3030

31-
1. Click the [**Insights**]({{ repoUrl }}/insights) tab in your repository
32-
1. On the left hand navigation bar, click **Dependency graph**
33-
1. Scroll down until you see a yellow bar highlighting the dependency named `debug`, and click on the right hand side of the yellow `debug` section
34-
1. Take note of the suggested version
35-
1. Comment in this issue with the suggested update version
31+
1. Click the **Insights** tab in your repository
32+
2. On the left hand navigation bar, click **Dependency graph**
33+
3. Scroll down until you see a yellow bar highlighting the dependency named `debug`, and click on the right hand side of the yellow `debug` section
34+
4. Take note of the suggested version
35+
5. Comment in this issue with the suggested update version
3636

3737

3838
> _**GitHub Enterprise Server only:** This is all possible on GitHub Enterprise through GitHub Connect. It may take up to an hour to refresh the alerts and make them visible. After waiting a reasonable amount of time, if you are still not seeing the yellow bar in the Dependency Graph, you may want to contact your administrator. In the mean time, to move along with the course, we'll give you a hint - the recommended upgraded version is `2.6.9`._

0 commit comments

Comments
 (0)