channable / channable/opsqueue
Check in CI that `Cargo.lock` is up-to-date
Open
- Dominant language
- Rust
- Stars
- 96
- Forks
- 2
- Avg merge
- 1h 2m
- Merged PRs (30d)
- 2
Description
See https://github.com/channable/opsqueue/pull/26 for a case where CI didn't check this.
It probably suffices to check that it is unchanged after e.g. `cargo build`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repository's CI configuration and the case described in pull request 26, then run the suggested cargo build locally. The work is done when CI detects any change to Cargo.lock after the build and fails accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100