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

Unlock this course with a free trial

Join today to access over 24,700 courses taught by industry experts.

Describe how code scanning relates to GitHub Actions consumption

Describe how code scanning relates to GitHub Actions consumption - GitHub Tutorial

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

Start my 1-month free trial Buy for my team

Describe how code scanning relates to GitHub Actions consumption

“

- [Tim] You might wonder, Tim, hang on. So you're saying that when, because CodeQL and code-scanning requires GitHub actions and therefore requires a workflow and therefore requires GitHub hosted Cloud Runners, is this costing us money outside of our GHAS license?" And the answer is, potentially. Remember, public repos are covered, but GitHub actions has a free tier, but you're paying for those runtime minutes. The resources that you're using in those cloud-hosted runners consume minutes that you pay for when you go above your allotment based on your specific license type. So, GitHub would recommend that you optimize your workflows for efficient scanning, make sure that your triggers are scoped granularly enough that you're not firing the workflow when you don't want to or you don't need to. And also you can disable workflows, so that'll save you money if you don't need the workflow for a time. You also can set the workflow_dispatch trigger in your workflow, and that's just basically…

Contents