Integrating CodeScan with Github Actions
  • 29 Sep 2022
  • 2 Minutes to read
  • Contributors
  • Dark

Integrating CodeScan with Github Actions

  • Dark

Point to Note:

The creation of the project in CodeScan creates a webhook in GitHub.

This webhook triggers on pushes to your tracked branch and certain pull request actions. These are: pull request opened, reopened, synchronized.
The pull request triggers allow your comparisons in CodeScan to be kept up to date if the pull request is updated.

Running CodeScan SCA jobs from Github Workflow

You can now run CodeScan static code analysis jobs from Github workflow. The codescan action will produce a SARIF report file with the analysis result.

There are only a few lines to add to your .YML file for codescan to be triggered.

First, we'll need to add your CodeScan token as a variable we can access in our .YML file.

  • Open your project and navigate to Repository Settings > Secrets > Add new secret.
  • Add your token with the name codescan_token and check the Secured box. To learn how to generate a token, see here.

Now you'll be able to access this variable by using $codescan_token in your .YML file.

If you do not have a workflow setup on your GitHub Repository, go to Actions > New workflow to create a .yml workflow.

Add the following into your .YML file in the workflow:

name: CI
    branches: [main]
    branches: [main]
    runs-on: ubuntu-latest
      - name: Checkout repository
        uses: actions/checkout@v2
      - name: Cache files
        uses: actions/cache@v2
            path: |
            key: ${{ runner.os }}-sonar
            restore-keys: ${{ runner.os }}-sonar
      - name: Run Codescan On Push
        if: github.event_name == 'push'
        uses: codescan-io/codescan-scanner-action@1.3
          organization: ‘Enter organization key here’
          projectKey: ‘Enter project key here’       
          login: ${{ secrets.codescan_token }}
      - name: Run Codescan On PR
        if: github.event_name == 'pull_request'
        uses: codescan-io/codescan-scanner-action@1.3
          organization: ‘Enter organization key here’
          projectKey: ‘Enter project key here’
          login: ${{ secrets.codescan_token }}
          args: |
      - name: Upload SARIF file
          uses: github/codeql-action/upload-sarif@v2
            sarif_file: codescan.sarif

You will need to replace the placeholder variables (in single quotes) in the env section of the script with your Project Key and Organization Key.

Now, you will be able to view the .yml workflow on your Repository.

And also check for the name of the master branch on both CodeScan platform and Git repository, as the new Git update changed the name of master branch to main.

If the name on CodeScan platform is not the same as Git Repository, go to your CodeScan project and then navigate to Dashboard > Administration > Branches & Pull Requests > Actions and change the branch name.

The branches names and comparisons are set by the following parameters:

  • sonar.pullrequest.key: The pull request number
  • sonar.pullrequest.base: The comparison branch for pull request type branches
  • sonar.pullrequest.branch: The name of the branch

The uploaded SARIF file in the .yml helps you to get the code analysis reports in two ways:

  1. For the files already existing in the repository, results can be found under code scanning alerts under the Security tab on GitHub repository.

  2. For the new files being uploaded to the repository, you can view the analysis during the pull-requests on GitHub by clicking on the details:

    • Select the relevant pull-request and then click on Details.

    • Once you click on the Details, go to Code scanning results > CodeScan.

    • Results are categorized as follows:

      • All the bugs and vulnerabilities are marked as ERRORS.
      • Whereas, all the major and minor code smells are marked as WARNINGS.

This .yml file helps you to run an analysis on the project while linking it to CodeScan.

You can go to the CI workflow under Git actions to view the analysis.

Was this article helpful?