Change string 'Modules to enable' to {@inheritdoc} in comments

Seems straight forward. The addition to subtraction is equal and spot checked a few dozen.

Wondering if this should just be @inheritdoc in most cases except where we add additional information?

Is true most could probably use that and the @var part

Moving back to needs review, I think I agree with #5 but if we're going to change to that, we might as well do that here?

Used the following to make the conversion to inheritdoc.

grep -r "* Modules to install." core | awk -F: '{print $1}' | xargs sed -z -i 's#Modules to install.\n   \*\n   \* @var array#{@inheritdoc}#' 
grep -r "* Modules to install." core | awk -F: '{print $1}' | xargs sed -z -i 's#Modules to install.\n   \*\n   \* @var string\[\]#{@inheritdoc}#' 

Then found remaining one with a simple search and did them by hand.

There is one remaining instance of 'modules to enable' but since that is not in a comment let's do that in a separate issue.

$ git grep -i 'modules to enable'
core/lib/Drupal/Core/Installer/Exception/NoProfilesException.php:    $message = $this->t('We were unable to find any installation profiles. Installation profiles tell us what modules to enable and what schema to install in the database. A profile is necessary to continue with the installation process.');

Looks great.

Just a rebase with no conflicts

There is one "module to enable" left in EntityDefinitionUpdateProviderTest without additional information, it was added last week so makes sense it got missed.

RTBC +1

Decided to backport this one to all active branches as a docs-only fix and to keep things in sync given that it touches a lot of files, otherwise it will make future cherry-picks more tricky in some cases.

longwave → closed merge request !9151

Automatically closed - issue fixed for 2 weeks with no activity.