Cannot display code coverage report if artifacts from target branch have expired

fgrosse / go-coverage-report

A CLI tool and GitHub Action to post Go code coverage reports as comment to your pull requests.

BSD 3-Clause "New" or "Revised" License

56 stars 10 forks source link

Cannot display code coverage report if artifacts from target branch have expired #5

Open fgrosse opened 7 months ago

fgrosse commented 7 months ago

It may happen that the uploaded code coverage artifact has expired already when we run the action. This is likely on repositories which do not receive changes frequently and thus, when a PR is opened, the code coverage from main will be missing.

fgrosse commented 7 months ago

GitHub actions artifacts by default expire after 90 days (which is also the maximum).

bejelith commented 2 months ago

This is also a problem when initialing a new repository, the coverage report fails because main has never reported before - in this case better then failing would be nice to just have the current code coverage values imho.

wmcnamee-coreweave commented 3 weeks ago

I just ran into this same problem. Not a great first impression. :(