Closed therealak12 closed 3 years ago
Thanks for the contribution! Before we can merge this, we need @therealak12 to sign the Sonatype Contributor License Agreement.
@therealak12 Thanks for this PR. I noticed our CI was not configured to build from forks. I've fixed that, but then noticed the build failing for this PR. Could you take a look and see if you can fix that failure?
FWIW, you can likely reproduce the CI error locally by following these steps: CI Debug Notes
I was able to reproduce the error locally using these steps.
@bhamail I fixed the CI errors. Would you please check again?
@therealak12 I have attempted to force a change in order to trigger the CI build.
@therealak12 That was odd. Anyway, it looks like CI is behaving now.
@therealak12 So there was still something odd going on with CircleCI. The build did trigger from your new commits, but ended with a message: We have detected an anomaly that violates the CircleCI Terms of Service.
The CircleCI folks mentioned if it happened again, you could reach out to them directly and "appeal the block".
Meanwhile, I've committed another silly change to trigger the full build. I will do the same on PR #56.
@therealak12 if you wanna come chat with us on gitter, I'd love to maybe send you some stickers for doing such awesome stuff: https://gitter.im/sonatype/nexus-developers
@therealak12 @bhamail and I were looking at STUFF and we think this library might be able to help out with parsing the files: https://pypi.org/project/requirements-parser/
Someone may need to only investigate packages listed in requirements file. This PR addresses this issue.
This pull request makes the following changes:
cc @bhamail / @DarthHater