4 ms·
Feels like we need a single command for that, I have two goals for my workflow (like maybe bininstall should be included in Cargo): 1) what’s the easiest way t
by bluejekyll 3y ago
Feels like we need a single command for that, I have two goals for my workflow (like maybe bininstall should be included in Cargo):
1) what’s the easiest way to give people access to a tool I just wrote, `cargo publish`
2) what’s the easiest way for someone to use it, as few steps as possible, right now it’s `install rust` && `cargo install`.
Once I get to three or more steps on 2 I tend to turn to just or make depending on the context.
- shzhdbi09gv8ioi 3y agoYou should combine step 1 and 2 in CI. Just tag a version in your git, push to remote and have CI auto build a release for you. Use github actions or other setup for other backends. (this is language agnostic and a reasonable thing to learn as a dev). Or if you must live in the cargo command, go nuts with cargo-release. https://github.com/crate-ci/cargo-release https://github.com/crate-ci/cargo-release https://github.com/cargo-bins/release-pr https://github.com/cargo-bins/release-pr