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: .github/workflows/codeql.yml
+14-12Lines changed: 14 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -49,14 +49,14 @@ jobs:
49
49
include:
50
50
- language: actions
51
51
build-mode: none
52
-
# CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
53
-
# Use `c-cpp` to analyze code written in C, C++ or both
54
-
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
55
-
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
56
-
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
57
-
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
58
-
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
59
-
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
52
+
# CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
53
+
# Use `c-cpp` to analyze code written in C, C++ or both
54
+
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
55
+
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
56
+
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
57
+
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
58
+
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
59
+
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
60
60
steps:
61
61
- name: Harden the runner (Audit all outbound calls)
# By default, queries listed here will override any specified in a config file.
86
86
# Prefix the list here with "+" to use these queries and those in the config file.
87
87
88
-
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
89
-
# queries: security-extended,security-and-quality
90
-
91
88
# If the analyze step fails for one of the languages you are analyzing with
92
89
# "We were unable to automatically build your code", modify the matrix above
90
+
93
91
# to set the build mode to "manual" for that language. Then modify this step
94
92
# to build your code.
95
93
# ℹ️ Command-line programs to run using the OS shell.
96
94
# 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
97
95
- if: matrix.build-mode == 'manual'
96
+
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
97
+
# queries: security-extended,security-and-quality
98
+
98
99
shell: bash
99
100
run: |
100
101
echo 'If you are using a "manual" build mode for one or more of the' \
101
102
'languages you are analyzing, replace this with the commands to build' \
0 commit comments