From the course: GitHub Advanced Security Cert Prep by Microsoft Press

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Contrast the steps to execute code scanning in GitHub Actions vs. the CodeQL CLI

Contrast the steps to execute code scanning in GitHub Actions vs. the CodeQL CLI - GitHub Tutorial

From the course: GitHub Advanced Security Cert Prep by Microsoft Press

Start my 1-month free trial Buy for my team

Contrast the steps to execute code scanning in GitHub Actions vs. the CodeQL CLI

“

- [Instructor] Yeah, all right. This is a a good exam alert type question I could see GitHub asking you on the exam. When would you choose to do your CodeQL locally on your own machine using the CLI versus GitHub Actions? Well, GitHub Actions is all about automation and automated scanning, continuous integration. There's that answer. CodeQL CLI is something you can leverage optionally at your desktop for manual scanning. This gives you maximal flexibility and control. It's good for quick checks, specific needs and also frankly, for research that you could then add into your GitHub Actions workflows. All right, this was a long lesson in terms of number of objectives. Let's get into our demo. This demonstration is about accessing your QL files and your workflows wherever they might be. And speaking of which, I found a really great repo that GitHub publishes here. It's github/vscode-codeql-starter. And this is a Visual Studio Code workspace that makes it a lot easier to get started with…

Contents