-
Notifications
You must be signed in to change notification settings - Fork 30
[TASK] Migrate composer normalize command to runTests.sh
#1901
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
base: main
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 19829009522Details
💛 - Coveralls |
5ab44ed to
8fe0305
Compare
8fe0305 to
c504718
Compare
|
Split normalize command in two. One check and one fix. |
One for check and one for fix Related: #1751
74952de to
603deeb
Compare
| command: | ||
| - "phpmd" | ||
| - "checkComposerNormalize" | ||
| - "fixComposerNormalize" |
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.
I think that only checkComposerNormalize belongs into the static-code-analysis job (and that it warrants its own entry in the test matrix).
Still, I think it would be worthwhile to also check in CI that our fix scripts can at least be run without errors. I propose we add a separate job checkFixers that will run all existing fixers one after another, with fixComposerNormalize as a start as part of this PR. What do you think?
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.
checkFixers? Nice idea. This should be done in another issue I think, right?
For this PR I remove the checkComposerNormalize command.
runTests.sh
Part of #1751