-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add details for running against pipenv projects #364
Conversation
CC @woodruffw |
@woodruffw @di Edit: Oh, I see you linked the relevant issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's break this out a bit: I think we want a separate "Tips and tricks" section, with this as a subsection.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @ameily!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some nits
Co-authored-by: Dustin Ingram <[email protected]>
Sorry, one last nit 😅 -- otherwise LGTM. |
Co-authored-by: William Woodruff <[email protected]>
I have a pipenv project that I wanted to run pip-audit against. I found a simple workaround to convert the
Pipfile[.lock]
to a compatiblerequirements.txt
file that pip-audit can process. I documented how I got this working in hopes it can help others with pipenv based projects. I've verified that the commands I added work properly, for both running locally and within GitHub CI.Refs #85