[ci] Stop autogenerating ruleset from branch differences#3399
Merged
Conversation
This prevents failing rules in pmd 7 to make the regression tester fail entirely.
Generated by 🚫 Danger |
adangel
approved these changes
Jul 15, 2021
adangel
left a comment
Member
There was a problem hiding this comment.
Thanks! I'll give it a try.
All not update rules will appear as missing from now on....
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
2 participants
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.
Describe the PR
This prevents failing rules in pmd 7 to make the regression tester fail entirely. This is a stopgap, that we can revert when all rules have been ported (#2701)
Related issues
The following PRs have recently had problems in CI that this should "solve":
Ready?
./mvnw clean verifypasses (checked automatically by github actions)