[Feature Request]: Pull diff coverage report from CI artifact

[planetmarshall]

Feature description

Hi - thanks for providing this action!

Would you accept a PR for a feature where the coverage report for comparison is retrieved from a CI artifact instead of a storage branch?

I was thinking along the lines of something like:

- name: Produce the coverage report
   uses: insightsengineering/coverage-action@v3
   with:
     diff-branch: main
     diff-workflow: run-tests
     diff-artifact: coverage-*

Where if specified the latest run of diff-workflow for diff-branch is checked for an artifact matching coverage-* to use for comparison.

The default for diff-workflow would be the empty string in which case diff-storage is used.

Code of Conduct

• I agree to follow this project's Code of Conduct.

Contribution Guidelines

• I agree to follow this project's Contribution Guidelines.

Security Policy

• I agree to follow this project's Security Policy.

[cicdguy]

Hi @planetmarshall – thanks for reporting this issue.

We had originally considered adding this feature, but ultimately decided against it. Artifacts in GitHub Actions are ephemeral, and retrieving their IDs across different workflows is nearly impossible without leveraging the GitHub GraphQL or REST Pipeline APIs. This approach would require the use of GitHub Personal Access Tokens (PATs) within the workflow, which we believe shouldn't be necessary for most use cases.

[planetmarshall]

Hi - thanks for the response. Good point on artifacts having a limited lifespan.