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
The current select is actually quite bad and it gets slower over
time since it basically querys the whole table until it found
200 rows.
This already made this script getting somewhat slow on beta
cluster where the biggest wiki has 3 million rows in revision.
Bug: T299954
Change-Id: I7add43d8005ab54a566813d36cf4544911bda6a6
Introduce migrateRevisionCommentTemp which copies data from
revision_comment_temp to rev_comment_id. The code is similar to
migrateRevisionActorTemp.php.
Bug: T299954
Change-Id: I3140d7efb18d4dfda783831ecb1549262e4bdc32