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: _labs/lab1.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,7 @@ Although Dependabot isn't part of the GitHub Advanced Security product suite, it
49
49
1. Next, let's enable **Code Scanning with CodeQL**. These settings are also under the **Code security** settings page.
50
50
2. Click the **Enable** button next to GitHub Advanced Security.
51
51
3. A prompt will confirm that you want to **Enable GitHub Advanced Security for this repository** - click the button.
52
+
- The prompt tells you how many GitHub Advanced Security licenses you would consume by enabling this feature - which is useful if you are an organization owner and want to ensure you have enough licenses for your organization.
52
53
4. Underneath the GitHub Advanced Security | Code Scanning heading, click the **Set up** button in the **CodeQL analysis** row.
53
54
5. There are two options: **Default** and **Advanced**. Select the **Default** option and review the settings.
54
55
- For this lab, we will use the **Default** setup which creates a managed Actions workflow (i.e. you will not see a file committed to the repo). You can use the Advanced option to manage your code scanning workflow as a GitHub Actions workflow YAML file committed to the repo. The **Default** option is a great option to get started quickly to enable code scanning in a repository without needing to commit any additional code.
0 commit comments