`fix-lock-files --check` doesn't fail when it should, just leaves a diff
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5
- Forks
- 1
- Avg merge
- 17h 48m
- Merged PRs (30d)
- 2
Description
I'm trying to run cargo fslabscli fix-lock-files --check on the main branch of fsl_libs right now, and it succeeds while producing a diff.
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 running cargo fslabscli fix-lock-files --check on the main branch of fsl_libs and inspect the diff it produces. Trace the check command's exit status and make it fail when the command would leave a diff, then verify that the command reports failure in this case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100