-
Notifications
You must be signed in to change notification settings - Fork 47
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
GitHub action #68
Comments
This is an interesting idea. |
Was just looking for exactly this, +1 from me |
I needed this so I took a stab at it, borrowing heavily from actions-rs. https://github.com/aig787/cargo-udeps-action. I'm happy to have it brought into the family if you want @est31. |
@est31 I build a simple workflow for running cargo-udeps in GitHub Actions. It wouldn't have to build a dedicated action IMO. https://github.com/engula/engula/runs/4332111979?check_suite_focus=true However, installing cargo-udeps takes about 5 minutes. Could we reduce the overhead? |
You could reduce it by caching built binary. |
Yeah there is a Rust specific section in the github actions cache documentation. |
Would there be an interest to roll out a GitHub action for
cargo-udeps
so that adding this one to CI runs would be just a one-liner?There is an awesome template by embark guys with their
cargo-deny
sanitizer we could use as a reference, which is nothing more than a Dockerfile and 3-4 lines of bash at it's core (link)There is also an opened issue to think about somehow merging
deny
andudeps
both together, but this is yet another topic :DThe action will probably reside in a separate repo (since it involves tagging versions of the action and this may interfere with
cargo-udeps
cli releases).The text was updated successfully, but these errors were encountered: