GitHub Actions

note

fetch-depth: 0 is required for checkout in case Qodana works in pull request mode (reports issues that appeared only in that pull request).

We recommend that you have a separate workflow file for Qodana because different jobs run in parallel

Gif

To make Qodana automatically fix found issues and push the changes to your repository, you need to

1. Choose what kind of fixes to apply

   • Specify fixesStrategy in the qodana.yaml file in your repository root

   • Or set the action args property with the quick-fix strategy to use: --apply-fixes or --cleanup

2. Set push-fixes property to

   • pull-request: create a new branch with fixes and create a pull request to the original branch

   • or branch: push fixes to the original branch. Also, set pr-mode to false: currently, this mode is not supported for applying fixes.

3. Set the correct permissions for the job (contents: write, pull-requests: write, checks: write)

   • If you use pull-request value for push-fixes property: allow GitHub Actions to create and approve pull requests

Example configuration:

- name: Qodana Scan
  uses: JetBrains/qodana-action@v2024.1
  with:
    pr-mode: false
    args: --apply-fixes
    push-fixes: pull-request
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

tip

Note Qodana could automatically modify not only the code, but also the configuration in .idea: if you do not wish to push these changes, add .idea to your .gitignore file.

You can set up GitHub code scanning for your project using Qodana. To do it, add these lines to the code_quality.yml workflow file right below the basic configuration of Qodana Scan:

- uses: github/codeql-action/upload-sarif@v2
  with:
    sarif_file: ${{ runner.temp }}/qodana/results/qodana.sarif.json

This sample invokes codeql-action for uploading a SARIF-formatted Qodana report to GitHub, and specifies the report file using the sarif_file key.

tip

GitHub code scanning does not export inspection results to third-party tools, which means that you cannot use this data for further processing by Qodana. In this case, you have to set up a baseline and quality gate processing on the Qodana side prior to submitting inspection results to GitHub code scanning, see the Quality gate and baseline section for details.

You can enforce GitHub to block the merge of pull requests if a quality gate has failed. To do it, create a branch protection rule as described below:

1. Create a new or open an existing GitHub workflow that invokes the Qodana Scan action.

2. Set the workflow to run on pull_request events that target the main branch.

on:
  pull_request:
    branches:
      - main

Instead of main, you can specify your branch here.

3. Set the number of problems (integer) for the Qodana action fail-threshold option.

4. Under your repository name, click Settings.

5. On the left menu, click Branches.

6. In the branch protection rules section, click Add rule.

7. Add main to Branch name pattern.

8. Select Require status checks to pass before merging.

9. Search for the Qodana status check, then check it.

10. Click Create.

You can combine the quality gate and baseline features to manage your technical debt, report only new problems, and block pull requests that contain too many problems.

Follow these steps to establish a baseline for your project:

1. Run Qodana locally over your project:

cd project
qodana scan \
   -e QODANA_TOKEN="<cloud-project-token>" \
   --show-report

2. Open your report at http://localhost:8080/, add detected problems to the baseline, and download the qodana.sarif.json file.

3. Upload the qodana.sarif.json file to your project root folder on GitHub.

4. Append the --baseline,qodana.sarif.json argument to the Qodana Scan action configuration args parameter in the code_quality.yml file:

- name: Qodana Scan
  uses: JetBrains/qodana-action@main
  with:
    args: --baseline,qodana.sarif.json

If you want to update the baseline, you need to repeat these steps once again.

Starting from this, GitHub will generate alters only for the problems that were not added to the baseline as new.

To establish a quality gate additionally to a baseline, add this line to code_quality.yml right after the baseline-path line:

fail-threshold: <number-of-accepted-problems>

Based on this, you will be able to detect only new problems in pull requests that fall beyond the baseline. At the same time, pull requests with new problems exceeding the fail-threshold limit will be blocked, and the workflow will fail.

You can set up a Qodana workflow badge in your repository, to do it, follow these steps:

1. Navigate to the workflow run that you previously configured.

2. On the workflow page, select Create status badge.

3. Copy the Markdown text to your repository README file.