github/codeql-action
1
0
Fork 0
mirror of https://github.com/github/codeql-action.git synced 2025-12-29 02:30:11 +08:00
Code Issues Packages Projects Releases Wiki Activity
5,860 Commits 297 Branches 500 Tags
codeql-bundle-v2.19.1
Commit Graph

11 Commits

Author SHA1 Message Date
Henry Mercer
94acfdc22c Upload SARIF with ref/sha inputs: Generate SARIF with analyze Action 2024-06-11 20:22:17 +01:00
Henry Mercer
485d096a80 Update upload-sarif ref/sha input test 
We are already testing the analyze Action in a separate check.
 2024-06-11 19:29:39 +01:00
Henry Mercer
12243c759f Disable database upload in test mode 2024-06-11 19:07:13 +01:00
Henry Mercer
d52a751f8f Only run ref and sha input checks against a single CLI version 
These checks aren't affected by the CLI version, so just run them with
the default CLI.
 2023-10-09 12:09:21 +01:00
Angela P Wen
a21bb7f968 Update upload input values and logic (#1598) 
- The `upload` input to the `analyze` Action now accepts the following values:
    - `always` is the default value, which uploads the SARIF file to Code Scanning for successful and failed runs.
    - `failure-only` is recommended for customers post-processing the SARIF file before uploading it to Code Scanning. This option uploads debugging information to Code Scanning for failed runs to improve the debugging experience.
    - `never` avoids uploading the SARIF file to Code Scanning even if the code scanning run fails. This is not recommended for external users since it complicates debugging.
    - The legacy `true` and `false` options will be interpreted as `always` and `failure-only` respectively.

---------

Co-authored-by: Henry Mercer <henry.mercer@me.com>
 2023-03-23 17:23:25 +00:00
Andrew Eisenberg
c208575433 Avoid uploading databases after integration tests 
We are still getting coverage of the upload capability through the
standard codeql analysis workflow.
 2023-03-14 14:55:58 -07:00
Henry Mercer
a190d3876a Rename TEST_MODE to specific variable for CodeQL Action 
This allows us to set it automatically in the workflow generator,
simplifying things and reducing the scope for error.
 2022-11-16 16:40:30 +00:00
Henry Mercer
96a8424f0c Don't bypass the toolcache in test mode 2022-08-16 16:18:12 +01:00
Edoardo Pirovano
8ec6a84629 Expand PR checks to cover windows-2022 2022-02-28 15:39:34 +00:00
Henry Mercer
b8047e5610 Use windows-2019 for CI jobs involving build tracing 
Build tracing currently does not support Windows 2022, so use
`windows-2019` instead of`windows-latest`.
 2022-02-08 13:29:20 +00:00
Alex Croteau
9f36b75178 Splits integration tests 2022-01-31 20:06:18 -05:00