7862ca3f86
Bumps [step-security/harden-runner](https://github.com/step-security/harden-runner) from 2.11.0 to 2.12.0.
- [Release notes](https://github.com/step-security/harden-runner/releases)
- [Commits](4d991eb9b9...0634a2670c)
---
updated-dependencies:
- dependency-name: step-security/harden-runner
dependency-version: 2.12.0
dependency-type: direct:production
update-type: version-update:semver-minor
...
Signed-off-by: dependabot[bot] <support@github.com>
62 lines
2.6 KiB
YAML
62 lines
2.6 KiB
YAML
# This workflow uses actions that are not certified by GitHub.
|
|
# They are provided by a third-party and are governed by
|
|
# separate terms of service, privacy policy, and support
|
|
# documentation.
|
|
|
|
# This workflow helps you trigger a SonarCloud analysis of your code and populates
|
|
# GitHub Code Scanning alerts with the vulnerabilities found.
|
|
# Free for open source project.
|
|
|
|
# 1. Login to SonarCloud.io using your GitHub account
|
|
|
|
# 2. Import your project on SonarCloud
|
|
# * Add your GitHub organization first, then add your repository as a new project.
|
|
# * Please note that many languages are eligible for automatic analysis,
|
|
# which means that the analysis will start automatically without the need to set up GitHub Actions.
|
|
# * This behavior can be changed in Administration > Analysis Method.
|
|
#
|
|
# 3. Follow the SonarCloud in-product tutorial
|
|
# * a. Copy/paste the Project Key and the Organization Key into the args parameter below
|
|
# (You'll find this information in SonarCloud. Click on "Information" at the bottom left)
|
|
#
|
|
# * b. Generate a new token and add it to your Github repository's secrets using the name SONAR_TOKEN
|
|
# (On SonarCloud, click on your avatar on top-right > My account > Security
|
|
# or go directly to https://sonarcloud.io/account/security/)
|
|
|
|
# Feel free to take a look at our documentation (https://docs.sonarcloud.io/getting-started/github/)
|
|
# or reach out to our community forum if you need some help (https://community.sonarsource.com/c/help/sc/9)
|
|
|
|
name: SonarCloud analysis
|
|
|
|
on:
|
|
push:
|
|
branches: [ "7.2" ]
|
|
pull_request:
|
|
branches: [ "7.2" ]
|
|
workflow_dispatch:
|
|
|
|
permissions:
|
|
pull-requests: read # allows SonarCloud to decorate PRs with analysis results
|
|
|
|
jobs:
|
|
Analysis:
|
|
runs-on: ubuntu-latest
|
|
|
|
steps:
|
|
- name: Block egress traffic
|
|
uses: step-security/harden-runner@0634a2670c59f64b4a01f0f96f84700a4088b9f0 # v2.12.0
|
|
with:
|
|
egress-policy: audit
|
|
|
|
- name: Checkout repository
|
|
uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7
|
|
with:
|
|
# Disabling shallow clone is recommended for improving relevancy of reporting
|
|
fetch-depth: 0
|
|
|
|
- name: Analyze with SonarCloud
|
|
uses: SonarSource/sonarqube-scan-action@v5.0.0
|
|
env:
|
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # Needed to get PR information
|
|
SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }} # Generate a token on Sonarcloud.io, add it to the secrets of this repo with the name SONAR_TOKEN (Settings > Secrets > Actions > add new repository secret)
|