The github actions depend on their being a lock file for stability

cberner / fuser

Filesystem in Userspace (FUSE) for Rust

MIT License

836 stars 114 forks source link

The github actions depend on their being a lock file for stability #118

Closed ianoc closed 3 years ago

ianoc commented 3 years ago

The github actions (old and new ones) all rely on the hash of a Cargo.lock file, the ci broke on master i believe because there is no lock file and its causing some cache pollution

ianoc commented 3 years ago

Well my understanding of what was happening with some of this turns out to be wrong, off. The on trigger for pull request is needed.

I've added it back to all the workflows to sit beside push. (I think on push, only works on the repo you push it to, so it doesn't show up on the PR if its in a different repo.[ideally I would have presumed this was the default in all this!]). Sorry @cberner my messup!

cberner commented 3 years ago

No worries. Thanks!