mirror of
https://github.com/asciinema/asciinema.git
synced 2026-04-25 07:55:51 +03:00
[PR #621] [CLOSED] add upload-rust-binary-action to upload build results #543
Labels
No labels
bug
compatibility
feature request
fit for beginners
help wanted
hosting
idea
improvement
packaging
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asciinema#543
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/asciinema/asciinema/pull/621
Author: @shawn111
Created: 2/18/2024
Status: ❌ Closed
Base:
develop← Head:develop📝 Commits (1)
6ea5ca8add upload-rust-binary-action to upload build results📊 Changes
2 files changed (+38 additions, -0 deletions)
View changed files
➕
.github/workflows/release.yml(+34 -0)📝
CHANGELOG.md(+4 -0)📄 Description
It's so great to see asciinema switch to Rust.
static binary is much easy to install.
Do you consider to enable upload-rust-binary-action to upload build release?
I just copy the example from https://github.com/taiki-e/upload-rust-binary-action
It supports cross-build.
Currently we just can cargo install.
I wish cargo binstall could work. https://github.com/cargo-bins/cargo-binstall
Here is my test build action: https://github.com/shawn111/asciinema/actions/runs/7950061837
Release binares:
https://github.com/shawn111/asciinema/releases/download/v0.0.1-alpha/asciinema-x86_64-unknown-linux-gnu.tar.gz
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.