| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
F–P. Still need to do P–Z.
there's a couple spots where I added `use
MediaWiki\Maintenance\LoggedUpdateMaintenance;` or similar instead.
some of the existing "use" blocks were in weird spots (e.g. above the copyright
docblock, or too far down). i didn't move those because they are out of scope
for this patch.
Change-Id: I5b6a8f3eae5be85d67bccfcce31c0c2027850f45
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Why:
* Maintenance scripts in core have bolierplate code that is
added before and after the class to allow directly running
the maintenance script.
* Running the maintenance script directly has been deprecated
since 1.40, so this boilerplate code is only to support a now
deprecated method of running maintenance scripts.
* This code cannot also be marked as covered, due to PHPUnit
not recognising code coverage for files.
* Therefore, it is best to ignore this boilerplate code in code
coverage reports as it cannot be marked as covered and also
is for deprecated code.
What:
* Wrap the boilerplate code (requiring Maintenance.php and then
later defining the maintenance script class and running if the
maintenance script was called directly) with @codeCoverageIgnore
comments.
* Some files use a different boilerplate code, however, these
should also be marked as ignored for coverage for the same
reason that coverage is not properly reported for files.
Bug: T371167
Change-Id: I32f5c6362dfb354149a48ce9c28da9a7fc494f7c
|
| |
|
|
|
| |
Bug: T353458
Change-Id: Ifa3b6a6e0353bb4ce21a3f4456f1fc696c8d377c
|
| |
|
|
|
| |
Bug: T363589
Change-Id: Ic89041ff6f145a73d39d81eb4a4fd9f238f7e576
|
| |
|
|
|
|
|
|
|
|
|
| |
Add an extension/skin attribute and a command line option for
manageForeignResources.php, for management of an extension's or
skin's foreign resources. This is less clumsy and more
introspectable than each extension/skin creating its own copy
of manageForeignResources.php.
Bug: T330508
Change-Id: I5df95ea4799d0efce60b58a35cb916c8e0f555b0
|
| |
|
|
|
|
|
| |
It literally has @ingroup ResourceLoader
Bug: T321882
Change-Id: Ia5c7c56c9235f98754f6d5e602da4626a76ff083
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable the equivalent of running `manageForeignResources.php verify`
as a structure test via PHPUnit.
Related cleanups for this to work well:
* Improve cache key readability before enabling in CI.
* Document how we do caching in CI.
* Change some exceptions to errors so that we don't
stop on the first error, thus improving the usefulness of the CI
result by telling the developer all mismatches instead of only
the first.
* Fix incorrect typehint for nullable $integrity.
Bug: T203694
Change-Id: I8aeffc1f2e81ffcf037977528f94c00995791999
|
| |
|
|
|
| |
Bug: T315311
Change-Id: Ia25c5413a2fd87c4cd75ddbbf7a02d1dba3581fd
|
| |
|
|
| |
Change-Id: I833052a656b1ce419c0929f6f0514f2a33c2c4cc
|
| |
|
|
| |
Change-Id: Ic6a4e42793d5f2d3e874e155ccbad1467e25698f
|
| |
|
|
|
|
|
|
|
|
|
| |
Previously, the help message was only shown when invoking the script
without parameters. Now, if invoking it with incorrect or mispelled
parameters, it shows what you can do instead (and no more exception trace,
which it did before).
Also document clearly but briefly how to use it, and with examples.
Change-Id: Ib5ba3dc02c54039495a33d6e0cc4d026ca708ba1
|
|
|
The maintenance script was previously in a subdirectory which
is a bit unusual. It's now a regular maintenance script,
with the YAML file in a more discoverable place as well.
Change-Id: I38690f23dbe89839bee0e1d43ecfd68adeb19c0f
|
