New command: verify Pipfile.lock hash is up to date #4896
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
fridex
reviewed
Dec 20, 2021
|
@den4uk Thanks for working on this, it currently requires more reviewers to chime in, but also I'm just realizing this should require some documentation and a news bit about its addition. |
Hi @matteius , I thought this may need some documentation being added 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This a proposal to have a new command added:
pipenv verifyThe aim is to be able to verify the hash in the Pipfile is up to date, or whether it needs updating.
The feature can be very useful within the CI/CD pipelines where the Pipfile.lock is a part of the repository and it needs to be up to date. The command can make it quick to run a check this is the case.
The PR is related to an open issue #4893