We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thanks for sharing and maintaining this action,
I have a workflow that downloads a bunch of outputs from other repositories.
For example, I select the master branch from ipfs/kubo.
My action failed with: https://github.com/ipfs/gateway-conformance/actions/runs/6218823800/job/16875980114
Run dawidd6/action-download-artifact@v2 ==> Repository: ipfs/kubo ==> Artifact name: gateway-conformance.json ==> Local path: ./ ==> Workflow name: gateway-conformance.yml ==> Workflow conclusion: completed ==> Branch: master ==> (found) Run ID: 62[1](https://github.com/ipfs/gateway-conformance/actions/runs/6218823800/job/16875980114#step:3:1)0849710 ==> (found) Run date: 2023-09-[17](https://github.com/ipfs/gateway-conformance/actions/runs/6218823800/job/16875980114#step:3:18)T01:42:28Z ==> (not found) Artifact: gateway-conformance.json ==> Found the following artifacts instead: Error: no artifacts found
When I open the run it's a run from the master branch of a fork. Which is not what I want to do. A fork could poison my workflow's output.
master
Related: ipfs/gateway-conformance#167
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Thanks for sharing and maintaining this action,
I have a workflow that downloads a bunch of outputs from other repositories.
For example, I select the master branch from ipfs/kubo.
My action failed with:
https://github.com/ipfs/gateway-conformance/actions/runs/6218823800/job/16875980114
When I open the run
it's a run from the
master
branch of a fork. Which is not what I want to do.A fork could poison my workflow's output.
Related: ipfs/gateway-conformance#167
The text was updated successfully, but these errors were encountered: