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
and at the following path in the CodeQL for Go repository::
124
119
125
-
ql/src/codeql-suites/go-lgtm.qls
120
+
ql/src/codeql-suites/go-code-scanning.qls
126
121
127
122
These locations are specified in the metadata included in the standard QL packs.
128
-
This means that CodeQL knows where to find the suite files automatically, and
123
+
This means that the CodeQL CLI knows where to find the suite files automatically, and
129
124
you don't have to specify the full path on the command line when running an
130
125
analysis. For more information, see ":ref:`About QL packs <standard-ql-packs>`."
131
126
132
-
For example, to run the LGTM.com query suite on a C++ codebase (generating
133
-
results in the latest SARIF format), you would run::
127
+
.. pull-quote::
128
+
129
+
Important
130
+
131
+
If you plan to upload the results to GitHub, you must generate SARIF results.
132
+
For more information, see `Analyzing a CodeQL database <https://docs.github.com/en/code-security/secure-coding/running-codeql-cli-in-your-ci-system#analyzing-a-codeql-database>`__ in the GitHub documentation.
133
+
134
+
For example, to run the code scanning query suite on a C++ codebase and generate
135
+
results in the v2.1 SARIF format supported by all versions of GitHub, you would run::
0 commit comments