Diff Coverage: The code coverage on the diff in this pull request is 85.7%.

Total Coverage: This PR will decrease coverage by 2.28%.

Diff Coverage: The code coverage on the diff in this pull request is 100.0%.

Total Coverage: This PR will not change total coverage.

1 new issue

@brynary Any chance you can tag a new version of this action please? I have a clover coverage file that is being misinterpreted as cobertura and the only way to resolve that is with the format option you introduced here.

Also, I have a situation which was previously supported with CodeClimate and wanted your thoughts on how to resolve it. Appreciate this may be more suitable for an issue, let me know if you would rather I report it there.

We have two separate test suites in one project that generate coverage files in clover and lcov format

      - name: Publish Qlty Code Coverage
        uses: qltysh/qlty-action/coverage@v1
        with:
          oidc: true
          skip-errors: 'false'
          files: ${{github.workspace}}/php-coverage/coverage.xml,${{github.workspace}}/cdk-coverage/lcov.info

With CodeClimate I could upload these in a single step by specifying the coverage format in the file path e.g. coverage.xml:clover and lcov.info:lcov respectively. Since the new format option applies to all files being uploaded, I've had to split the step into two steps like below

      - name: Publish PHP Code Coverage
        uses: qltysh/qlty-action/coverage@v1
        with:
          oidc: true
          skip-errors: 'false'
          format: clover
          total-parts-count: 2
          files: ${{github.workspace}}/php-coverage/coverage.xml

      - name: Publish CDK Code Coverage
        uses: qltysh/qlty-action/coverage@v1
        with:
          oidc: true
          skip-errors: 'false'
          format: lcov
          total-parts-count: 2
          files: ${{github.workspace}}/cdk-coverage/lcov.info

Is that the recommended approach? I haven't actually got it working yet since the format input is not available in v1.