New issue
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
Fix "reference not found" error #433
Conversation
If an action uses the branch to pin the major version, `- use: user/action@v1` will stop with an error: "v1: reference not found." In this case `act` should use refs/remotes/origin/v1 as a name to resolve v1 revision.
I'm very interested in getting this fixed as well, thanks for providing a pr @lufia . Testing locally, I'm still seeing failures. In this case I'm trying to use the jobs:
image:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: anchore/scan-action@main
with:
image: "python:3.8"
debug: true This fails in the same way as before:
|
@alfredodeza Thanks for your testing! I will check this case. |
I'm having the same problem with |
Hi. @alfredodeza I'm trying to represent the error. Unfortunately, I got success with above configuration.
Could I get the steps to reproduce? |
@lufia I'm not sure why I'm seeing Here is the yaml to reproduce: name: "Reproduce issue 433"
on: [push]
jobs:
image:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: anchore/scan-action@act-fails
with:
image: "python:3.8"
debug: true Save that as
|
@alfredodeza Thank you, I understand the problem. Act should checkout refs/remotes/origin/act-fails instead of refs/heads/act-fails. I will create a new pull request. |
If an action uses the branch to pin the major version, for example
- use: 8398a7/action-slack@v3
will stop with an error: "v3: reference not found."
In this case
act
should use refs/remotes/origin/v1 as a name to resolve v1 revision.#311
I checked:
- use: 8398a7/action-slack@v3