Firefly III: a personal finances manager
PHP accountingbudgetbudgetingbudgetscash-flowcashflowcredit-carddockerexpensesfinancefinancesfinanciallinuxmoneypaycheckpersonal-financephpphp7
Modify SonarCloud analysis workflow configuration
James Cole8875b0fc2f6e
diff --git a/.github/workflows/sonarcloud.yml b/.github/workflows/sonarcloud.ymlnew file mode 100644index 0000000000..147ad7b671--- /dev/null+++ b/.github/workflows/sonarcloud.yml@@ -0,0 +1,67 @@+# 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: Code - SonarCloud analysis++on:+ push:+ branches: [ "main", "develop" ]+ pull_request:+ branches: [ "main", "develop" ]+ workflow_dispatch:++permissions:+ pull-requests: read # allows SonarCloud to decorate PRs with analysis results++jobs:+ Analysis:+ runs-on: ubuntu-latest++ steps:+ - name: Analyze with SonarCloud++ # You can pin the exact commit or the version.+ # uses: SonarSource/[email protected]+ uses: SonarSource/sonarcloud-github-action@4006f663ecaf1f8093e8e4abb9227f6041f52216+ env:+ 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)+ with:+ # Additional arguments for the SonarScanner CLI+ args:+ # Unique keys of your project and organization. You can find them in SonarCloud > Information (bottom-left menu)+ # mandatory+ -Dsonar.projectKey=firefly-iii_firefly-iii+ -Dsonar.organization=firefly-iii+ # Comma-separated paths to directories containing main source files.+ #-Dsonar.sources= # optional, default is project base directory+ # Comma-separated paths to directories containing test source files.+ #-Dsonar.tests= # optional. For more info about Code Coverage, please refer to https://docs.sonarcloud.io/enriching/test-coverage/overview/+ # Adds more detail to both client and server-side analysis logs, activating DEBUG mode for the scanner, and adding client-side environment variables and system properties to the server-side log of analysis report processing.+ #-Dsonar.verbose= # optional, default is false+ # When you need the analysis to take place in a directory other than the one from which it was launched, default is .+ projectBaseDir: .