ci: name sonar and codeql jobs after their respective tools making them easier to distinguish on the ci report
This commit is contained in:
2
.github/workflows/codeql-analysis.yml
vendored
2
.github/workflows/codeql-analysis.yml
vendored
@ -24,7 +24,7 @@ on:
|
||||
- '!src/unittests/**'
|
||||
|
||||
jobs:
|
||||
analyze:
|
||||
codeql:
|
||||
runs-on: ubuntu-latest
|
||||
container: debian:trixie-slim
|
||||
timeout-minutes: 20
|
||||
|
||||
2
.github/workflows/sonarcloud-analysis.yml
vendored
2
.github/workflows/sonarcloud-analysis.yml
vendored
@ -25,7 +25,7 @@ on:
|
||||
- '!src/unittests/**'
|
||||
|
||||
jobs:
|
||||
analyze:
|
||||
sonar:
|
||||
# This job would fail for contributors who open PRs as the workflow runs outside of our repo
|
||||
# in this scenario. Having a var that only we set to true prevents this job from running.
|
||||
if: ${{ vars.SONAR_SCANNER_ENABLED }}
|
||||
|
||||
Reference in New Issue
Block a user