You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compiling cross on CI takes more time compared to pulling the binary directly from a GitHub release.
We can use taiki-e/install-action to pull the binary directly from the GitHub release. This action supports tagging a specific release or using the latest version.
However, I see that the CI currently pulls from the latest commit with --git, which requires compiling.
If you prefer using the latest release, I am ready to make a PR to switch to taiki-e/install-action.
Thank you for Iroh 🍜
The text was updated successfully, but these errors were encountered:
## Description
Quoting from #2394
> Compiling `cross` on CI takes more time compared to pulling the binary
directly from a GitHub release.
> We can use
[taiki-e/install-action](https://github.com/taiki-e/install-action) to
pull the binary directly from the GitHub release. This action supports
tagging a specific release or using the latest version.
## Breaking Changes
No.
## Notes & open questions
## Change checklist
- [ ] Self-review.
- [ ] Documentation updates if relevant.
- [ ] Tests if relevant.
- [ ] All breaking changes documented.
Closes#2394
Co-authored-by: Asmir Avdicevic <asmir.avdicevic64@gmail.com>
Hi, 👋
Compiling
cross
on CI takes more time compared to pulling the binary directly from a GitHub release.We can use taiki-e/install-action to pull the binary directly from the GitHub release. This action supports tagging a specific release or using the latest version.
However, I see that the CI currently pulls from the latest commit with
--git
, which requires compiling.If you prefer using the latest release, I am ready to make a PR to switch to
taiki-e/install-action
.Thank you for Iroh 🍜
The text was updated successfully, but these errors were encountered: