Add rule type to verify that a lockfile exists in a Python project #267
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
JAORMX
force-pushed
the
lockfile-python
branch
2 times, most recently
from
25f1ed8 to
216e2f4
Compare
rdimitrov
reviewed
Jan 13, 2025
JAORMX
force-pushed
the
lockfile-python
branch
from
216e2f4 to
60b1923
Compare
The idea is to have a catch-all rule that helps organizations enforce the usage of lockfiles. Signed-off-by: Juan Antonio Osorio <[email protected]>
JAORMX
force-pushed
the
lockfile-python
branch
from
60b1923 to
43d9a2b
Compare
rdimitrov
approved these changes
Jan 13, 2025
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.
The idea is to have a catch-all rule that helps organizations enforce
the usage of lockfiles.
Signed-off-by: Juan Antonio Osorio [email protected]