Conversation
Contributor
Author
maxrake
commented
May 19, 2022
maxrake
commented
May 19, 2022
maxrake
commented
May 19, 2022
kylewillmon
previously approved these changes
May 19, 2022
kylewillmon
approved these changes
May 19, 2022
This file contains hidden or 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
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
phylumPython package has been updated to offer the ability to analyze lockfile changes within the GitLab CI/CD environment. Merge requests (MRs) can be analyzed and annotated automatically when they include changes to a lockfile.The core logic and annotation strategy came from existing Phylum implementations:
The best bet for learning about the functionality added here is to start with the
README.mdanddocs/gitlab_ci.mddocumentation files. The code in this PR has been exposed as a Docker image and pushed to the phylumio/phylum-ci:gitlab tag. That image can be used to test locally or with your own GitLab private repository. In fact, it can be used now, for any customer that is hot to get started (CC: @furi0us333)Closes #31
Checklist
closes #<issueNum>in description above)?gitlabtag from Docker Hub after this PR is merged and a new release cut