killercup / killercup/cargo-edit
Support cargo-binstall
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.5k
- Forks
- 166
- PR merge metrics
- No merged PRs in 30d
Description
cargo-edit is pretty handy in CI contexts but compiling it each time can be a bit arduous.
It would be nice if cargo-edit supported using cargo-binstall via uploaded binaries to GitHub releases or similar. Being able to pull binaries directly would be much more handy for CI projects.
Contributor guide
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 reviewing cargo-edit's current release and build setup alongside cargo-binstall's requirements for uploaded binaries. Determine which GitHub release artifacts are needed for CI installation. Done means cargo-binstall can install cargo-edit directly from a GitHub release and the release process supports that path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100