-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Use taiki-e/install-action and binstall in CI #17573
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
Use taiki-e/install-action and binstall in CI #17573
Conversation
9a92103 to
5a63a6c
Compare
.github/workflows/audit.yml
Outdated
| - uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0 | ||
| - name: Install cargo-audit | ||
| run: cargo install cargo-audit | ||
| uses: taiki-e/install-action@v2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we put the version hash?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure, give me a second
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
blaginin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
|
It failed when I had it enabled. I somewhat doubt it would run well anyways given the machine constraints |
|
Got it! I think it's working now (and actually uses less resources as tools are not built), so going to merge if that's ok with everyone. I think we can iterate on top (as in adding |
Which issue does this PR close?
Rationale for this change
Should make CI faster. For example currently just installing
cargo-msrvtakes >5 minutes, with this PR its ~4 seconds.What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?