Set up workflows to add binaries for `divviup-cli` on github release
Open
Nobody has claimed this yet.
CLI
Ops/Admin
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
So that subscribers can download a binary release instead of needing a Rust toolchain and needing to compile the binary.
I think these platforms are a good starting point:
- Windows amd64
- MacOS aarch64
- MacOS amd64
- Linux amd64 (statically linked binary)
- Linux aarch64 (statically linked binary)
Additional considerations:
- Linux packaging--static binaries just get us started.
- App signing requirements for Windows and MacOS.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the GitHub release workflow and the divviup-cli build entry point. Done means release artifacts exist for the listed Windows, macOS, and Linux targets, with static Linux binaries; also review the open signing and Linux packaging considerations before treating the work as complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100