-
Notifications
You must be signed in to change notification settings - Fork 51
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
Update GitHub Action (on 2.0.15+1 vs. 2.0.20) to get fixed versions #93
Comments
Hi, thanks for this! I didn't realize I have to re-publish every version. I just clicked some buttons here on github.com and the published action is 2.0.20. Let me know if this doesn't fix your issue. |
Gah, I have no idea what this mean, unfortunately. There is not even a line 16 in For SEO, the error says:
|
Jep, running into the same issue sadly. It does not work to implement the action in a regular way or copy e.g. the command from the marketplace:
Therefore people are currently unable to use this great action out of the box and the important fix in 2.0.20 is not easily accessible. The GitHub CI is failing after 3s for me:
It looks like people using the action right now, manually install the 2.0.20 version from the repo and run the tool by hand in CI. Can you please try to look into this? @errnesto Maybe you've any ideas here? |
Hi,
I'm trying to call the GitHub action with multiple arguments, but if I get the changelog right that only works from version
2.0.20
onwards. But the latest action I can use from the marketplace is the one that is in the docs (2.0.15+1
)Using:
fails because the arguments are passed as one %-encoded argument. Maybe it's just a documentation problem how to pass multiple arguments to the GitHub action and how the versions relate.
I'm helping myself by directly addresssing the container to be able to work with the latest version but it feels hacky because undocumented
Given the simplicity of this solution it could be documented, too if there's some issue or blocker to automating the github action release on new releases.
The text was updated successfully, but these errors were encountered: