Skip to content

Conversation

@kanow
Copy link
Contributor

@kanow kanow commented Dec 1, 2025

Part of #1751

@kanow kanow requested a review from oliverklee December 1, 2025 15:10
@kanow kanow self-assigned this Dec 1, 2025
@coveralls
Copy link

coveralls commented Dec 1, 2025

Pull Request Test Coverage Report for Build 19829009522

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 19828117735: 0.0%
Covered Lines: 111
Relevant Lines: 111

💛 - Coveralls

@kanow kanow force-pushed the 1751-migrate-composer-normalize branch from 5ab44ed to 8fe0305 Compare December 1, 2025 15:16
@kanow kanow force-pushed the 1751-migrate-composer-normalize branch from 8fe0305 to c504718 Compare December 1, 2025 15:38
@kanow kanow added this to the 4.0.0: Breaking changes milestone Dec 1, 2025
@kanow kanow moved this to In review in Best Practices Remote Day Dec 1, 2025
@kanow kanow changed the title 1751 migrate composer normalize [TASK] Migrate composer normalize command in runTests Dec 1, 2025
@kanow
Copy link
Contributor Author

kanow commented Dec 1, 2025

Split normalize command in two. One check and one fix.

One for check and one for fix

Related: #1751
@kanow kanow force-pushed the 1751-migrate-composer-normalize branch from 74952de to 603deeb Compare December 1, 2025 16:01
command:
- "phpmd"
- "checkComposerNormalize"
- "fixComposerNormalize"
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@oliverklee oliverklee changed the title [TASK] Migrate composer normalize command in runTests [TASK] Migrate composer normalize command to runTests.sh Dec 1, 2025
@oliverklee oliverklee moved this from In review to In Progress in Best Practices Remote Day Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

3 participants