Change Details

It'd be really useful if when working on libraries like #iputils if you could do `check coverage` (like we do in MW core etc) to see if code coverage increased/decreased or stayed the same... And also just as part of the patch submission workflow if it was done automatically too ```lang=yaml - name: mediawiki/libs/IPUtils template: - name: composer-test-package-php72-or-later postmerge: - doxygen-publish - phpunit-coverage-php72-docker-publish ``` Presumably this will require adding a `phpunit-coverage-php72-patch-docker` to go with `phpunit-coverage-php72-docker-publish` like we do for `extension-coverage` ```lang=yaml - name: extension-coverage postmerge: - mwext-phpunit-coverage-docker-publish coverage: - mwext-phpunit-coverage-patch-docker ```

Numerous repositories have coverage reports, and as such, it'd be useful if CI ran the coverage difference checker both on patches, and also on demand using `check coverage` like we already do for MW core, extensions etc ```lang=yaml - name: mediawiki/libs/IPUtils template: - name: composer-test-package-php72-or-later postmerge: - doxygen-publish - phpunit-coverage-php72-docker-publish ``` Presumably this will require adding a `phpunit-coverage-php72-patch-docker` to go with `phpunit-coverage-php72-docker-publish` like we do for `extension-coverage` ```lang=yaml - name: extension-coverage postmerge: - mwext-phpunit-coverage-docker-publish coverage: - mwext-phpunit-coverage-patch-docker ```

It'd be really useful if when working on libraries like #iputils if you could do `check coverage` (like we do in MW core etc) to see if code coverage increased/decreased or stayed the same... And also just as part of the patch submission workflow if it was done automatically tooNumerous repositories have coverage reports, and as such, it'd be useful if CI ran the coverage difference checker both on patches, and also on demand using `check coverage` like we already do for MW core, extensions etc ```lang=yaml - name: mediawiki/libs/IPUtils template: - name: composer-test-package-php72-or-later postmerge: - doxygen-publish - phpunit-coverage-php72-docker-publish ``` Presumably this will require adding a `phpunit-coverage-php72-patch-docker` to go with `phpunit-coverage-php72-docker-publish` like we do for `extension-coverage` ```lang=yaml - name: extension-coverage postmerge: - mwext-phpunit-coverage-docker-publish coverage: - mwext-phpunit-coverage-patch-docker ```