paket restore does not fail by default on out-of-sync lock file
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
With an out-of-sync lock file, paket restore succeeds with return code of zero:
There is a flag to fail in this scenario, --fail-on-checks, but this requires opting in on every single invocation. For a large build system, this requires adding it to every paket build step definition in every codebase.
Can we make this fail by default? If there isn't something built-in already, I'd be interested in either of two possible changes:
- Invert the behaviour: Make it always fail by default and change the flag to
--ignore-check-failuresor similar. - Define an environment variable that can be set to enable
--fail-on-checksby default.
Thanks.
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 at the paket restore entry point and trace how the --fail-on-checks flag affects an out-of-sync lock file. Review the existing behavior and determine whether the completed change should make failures default or provide an environment-variable alternative; done means the chosen policy is applied consistently without requiring the flag on every invocation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100