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
Bug: binary.github prevents further manifest actions from running when it thinks no action is required. #287
Comments
Actually the workaround doens't work.. any other manifest coming after So looks like I have to delete the downloaded binary: ---
where: os.name == "linux"
actions:
- action: command.run
command: rm
args:
- "{{ user.home_dir }}/.local/share/bin/enact"
- action: binary.github
name: enact
directory: "{{ user.home_dir }}/.local/share/bin/"
repository: chmln/enact
version: v0.1
- action: directory.copy
from: enact
to: "{{ user.home_dir }}/.config/systemd/user/" |
This is fixed on the main branch. |
@rawkode how do I get a binary for the lates fixes? 👈🏻 rust noob. |
https://crates.io/crates/comtrya is broken, because we messed up the tag name and our action didn't run to make a release and nobody reran the whole shebang :D You could download comtrya here |
yeah I've already got that release. Does publishing a crate result in a executable that i can download and use on windows/linux and mac without installing rust? |
Nope, you have to install it via |
Description
If I have:
files/enact/enact.service
enact.yml
then:
1st run
both actions run2nd run
binary.github attempts, fails and nothing else in the manifest is processed.If I switch to:
Then it works.
This would obviously force certain workflows that depend on the installed binary to be split into two manifests.
Steps to reproduce
Try the above two manifests.
Expected behaviour
binary.github
should never cause the current manifest to bail/error/exit/prevent-further-actions/prevent-further-manifestsEnvironment
Fedora release 36 (Thirty Six)
5.19.15-201.fc36.x86_64
0.8.0
Additional information
Add more context which didn't fit in the fields above.
The text was updated successfully, but these errors were encountered: