Updated changelogs to link to the related issue.

[suralc]

This update should make the changelogs easier to handle from the github interface as no more copy+paste is required to read into specifics of an issue.

News entries on the homepage link to github, so it will always be rendered fine. This could probably be automated in the release process but also eases use of those logs while developing.

Script used. The regex should only match issues that are not yet linkified so running this multiple times should be fine.:

$changelogs = array_merge(['./framework/CHANGELOG.md'], glob('./extensions/*/CHANGELOG.md'));
$baseUrl = 'https://github.com/yiisoft/yii2/issues/';

foreach($changelogs as $log) {
    $content = file_get_contents($log);
    $content = preg_replace_callback('/(?P<issue>(?<!\\[)#[\\d]{1,4}(?<!\\]))/m', function($match) use ($baseUrl) {
        $issueNumber = trim(trim($match['issue'], '#'));
        return '[' . trim($match['issue']) . '](' . $baseUrl . urlencode($issueNumber) . ')';
    }, $content, -1, $count);
    file_put_contents($log, $content);
    echo 'Updated', $log, ' ', $count, ' occurences updated', PHP_EOL;
}

[lynicidn]

это не нужно все таск менегеры умеют читать #6733

[suralc]

@lynicidn I don't know how the other issue, your comment and this issue relate. I only brought up the idea of adding this to the release task (build/controllers/ReleaseController.php) to allow a quick automated fix if this change is desirable and someone adds a line without a link.

The links I added on the other issue are just to point out that the syntax is still valid on newer versions of phpdoc and the related standart proposal.

[qiangxue]

With these links, the raw changelog file is very cluttered. I think its' better we develop a changelog viewer that adds links dynamically.

[suralc]

Right, I only checked the last news entry which linked to the rendered file on github and most people around here don't use markdown as a plain text format, but default to opening it with some editor that can render it. That's probably not true for all environments, even if the linked version isn't that unreadable without an editor (as long one doesn't reads it on a shell).

Anyway, @qiangxue shall I close the pr or should it stay open, as you reopened it?

[qiangxue]

Let's keep it open. We will develop a changelog viewer in the new project site and may use your script here.

[klimov-paul]

After we extracted extensions into the separated repository this PR lost it sense.