kworkflow / kworkflow/patch-hub
add `cargo install` ci
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 36
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Description:
A Github workflow that runs cargo install --path . as well as cargo install patch-hub (if and when patch-hub is published to crates.io) to ensure that the commit did not break installation.
Motivation:
Even though we already have a workflow to run cargo build, cargo install does not use the lock file to determine version info. This can lead to different versions being installed and therefore has a chance of breaking as it did in #119.
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 reading the existing workflow that runs cargo build and identify where CI workflow configuration is kept. Add installation checks for cargo install --path . and, when available on crates.io, cargo install patch-hub; done means the workflow catches installation failures caused by dependency or version differences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100