feat!: remove SUCCESS
comments from PRs/MRs
#526
Merged
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 change removes the
SUCCESS
comments from pull requests (PRs) and merge requests (MRs). Other comment types are unchanged. This change is necessary because theSUCCESS
comments are considered by existing customers to be too noisy and not useful since the related status check will show as passing when the analyis is successful. Plus, the logs contain the same information as was included in theSUCCESS
comments.Closes #78
BREAKING CHANGE: PRs/MRs will no longer have
SUCCESS
comments.Checklist
closes #<issueNum>
in description above)?Testing
The changes in this PR are available for testing with the
maxrake/phylum-ci:quiet_wins
Docker image found on Docker Hub.This is what it looks like when a PR is created on GitHub with a lockfile that includes changes where the analysis is successful. Notice there is no comment.
This is what it looks like when the PR is updated to include a known bad dependency:
This is what it looks like when the PR is updated to remove the known bad dependency. Notice that the status check is green and there is no comment.
TODO
phylum-dev/phylum-analyze-pr-action
repo to account for the documentation updates needed for the GitHub action