Add more end-to-end tests for upload-sarif
#1
mbg__upload-sarif.yml
on: pull_request
Matrix: Test different uses of `upload-sarif`
Annotations
3 errors
|
Test different uses of `upload-sarif` (ubuntu-latest, default, code-quality)
Aborting upload: only one run of the codeql/analyze or codeql/upload-sarif actions is allowed per job per tool/category. The easiest fix is to specify a unique value for the `category` input. If .runs[].automationDetails.id is specified in the sarif file, that will take precedence over your configured `category`. Category: (.github/workflows/__upload-sarif.yml:upload-sarif/analysis-kinds:code-quality/os:ubuntu-latest/version:default/) Tool: (CodeQL)
|
|
Test different uses of `upload-sarif` (ubuntu-latest, default, code-scanning)
Aborting upload: only one run of the codeql/analyze or codeql/upload-sarif actions is allowed per job per tool/category. The easiest fix is to specify a unique value for the `category` input. If .runs[].automationDetails.id is specified in the sarif file, that will take precedence over your configured `category`. Category: (.github/workflows/__upload-sarif.yml:upload-sarif/analysis-kinds:code-scanning/os:ubuntu-latest/version:default/) Tool: (CodeQL)
|
|
Test different uses of `upload-sarif` (ubuntu-latest, default, code-scanning,code-quality)
Aborting upload: only one run of the codeql/analyze or codeql/upload-sarif actions is allowed per job per tool/category. The easiest fix is to specify a unique value for the `category` input. If .runs[].automationDetails.id is specified in the sarif file, that will take precedence over your configured `category`. Category: (.github/workflows/__upload-sarif.yml:upload-sarif/analysis-kinds:code-scanning,code-quality/os:ubuntu-latest/version:default/) Tool: (CodeQL)
|