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
-36Lines changed: 0 additions & 36 deletions
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,3 @@
1
-
# For most projects, this workflow file will not need changing; you simply need
2
-
# to commit it to your repository.
3
-
#
4
-
# You may wish to alter this file to override the set of languages analyzed,
5
-
# or to provide custom queries or build logic.
6
-
#
7
-
# ******** NOTE ********
8
-
# We have attempted to detect the languages in your repository. Please check
9
-
# the `language` matrix defined below to confirm you have the correct set of
10
-
# supported CodeQL languages.
11
-
#
12
1
name: "CodeQL Advanced"
13
2
14
3
on:
@@ -35,10 +24,6 @@ jobs:
35
24
# required to fetch internal or private CodeQL packs
36
25
packages: read
37
26
38
-
# only required for workflows in private repositories
39
-
actions: read
40
-
contents: read
41
-
42
27
strategy:
43
28
fail-fast: false
44
29
matrix:
@@ -55,37 +40,16 @@ jobs:
55
40
# (Unity generates Xcode/Android projects during build). CodeQL's C/C++ autobuilder
56
41
# doesn't recognize .mm (Objective-C++) files as source files. The minimal native
57
42
# bridge code is low-risk, and the main codebase (C#) is already being analyzed.
58
-
# CodeQL supports the following values keywords for 'language': 'actions', 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'rust', 'swift'
59
-
# Use `c-cpp` to analyze code written in C, C++ or both
60
-
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
61
-
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
62
-
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
63
-
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
64
-
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
65
-
# 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
66
43
steps:
67
44
- name: Checkout repository
68
45
uses: actions/checkout@v6
69
46
70
-
# Add any setup steps before running the `github/codeql-action/init` action.
71
-
# This includes steps like installing compilers or runtimes (`actions/setup-node`
72
-
# or others). This is typically only required for manual builds.
73
-
# - name: Setup runtime (example)
74
-
# uses: actions/setup-example@v1
75
-
76
47
# Initializes the CodeQL tools for scanning.
77
48
- name: Initialize CodeQL
78
49
uses: github/codeql-action/init@v4
79
50
with:
80
51
languages: ${{ matrix.language }}
81
52
build-mode: ${{ matrix.build-mode }}
82
-
# If you wish to specify custom queries, you can do so here or in a config file.
83
-
# By default, queries listed here will override any specified in a config file.
84
-
# Prefix the list here with "+" to use these queries and those in the config file.
85
-
86
-
# 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
87
-
# Consider enabling security queries for better coverage:
0 commit comments