coverallsapp / github-action

Coveralls Github Action
https://coveralls.io
MIT License
458 stars 76 forks source link

v2 doesn't work #159

Closed flatcap closed 1 year ago

flatcap commented 1 year ago

According to the README.md v2 is,

It is a pre-release but will become the main supported version soon.

This is my working v1 config:

- name: Coveralls
  uses: coverallsapp/github-action@master
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    path-to-lcov: coverage.info

I gave v2 a go:

- name: Coveralls
  uses: coverallsapp/github-action@v2
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    file: coverage.info

Failed:

๐Ÿ“„ Using coverage file: coverage.info โš ๏ธ Coverage reporter does not yet know how to process this file: coverage.info

Action log


The docs say that the file parameter is optional:

- name: Coveralls
  uses: coverallsapp/github-action@v2
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}

Failed:

Nothing to report

Action log


Let's try the old parameter, just in case:

- name: Coveralls
  uses: coverallsapp/github-action@v2
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    path-to-lcov: coverage.info

Failed:

๐Ÿ“„ Using coverage file: coverage.info โš ๏ธ Coverage reporter does not yet know how to process this file: coverage.info

Action log


What am I doing wrong? Thanks

flatcap commented 1 year ago

@Xyaneon is seems that we're missing the format param:

This works for me:

    - name: Coveralls
      uses: coverallsapp/github-action@v2
      with:
        github-token: ${{ secrets.GITHUB_TOKEN }}
        file: coverage.info
        format: lcov

Thanks to @snototter who figured it out.

flatcap commented 1 year ago

Coveralls: You need to mention this in UPDATE.md and document how actions work in coverage-reporter.

Xyaneon commented 1 year ago

@flatcap, I can confirm the same changes also work for me. Thanks to both you and @snototter! Hopefully Coveralls either updates their documentation or improves their file format detection.

mrexox commented 1 year ago

Thank you all! I've updated the UPGRADE.md with the recommendation to use format. I'll close this issue, since the problem is resolved.