i18n: Replace dead link in README.md.

[lephleg]

Fixes #29696.

Alters an irrelevant link in the i18n README.md file to a more proper entry.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @lephleg! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[talldan]

Thanks for your contribution @lephleg.

One of the checks is failing. I believe you'll need to run the npm run docs:build command from the command line to update the compiled version of the docs.

Commit and push that change and the check should pass.

[lephleg]

@talldan thanks for the assistance! I tried the npm run docs:build command but all it does is reverting my changes back to the original. That's the reason the static analysis is failing after running the above command. It's not clear to me yet why this is happening though.

Following @mkaz's extended guide along with the documentation Contributor's Guide I find no reference to additional steps required in order to update an existing document. I'll have to dig in to the build script itself.

[swissspidy]

@talldan thanks for the assistance! I tried the npm run docs:build command but all it does is reverting my changes back to the original. That's the reason the static analysis is failing after running the above command. It's not clear to me yet why this is happening though.

Following @mkaz's extended guide along with the documentation Contributor's Guide I find no reference to additional steps required in order to update an existing document. I'll have to dig in to the build script itself.

It's because you are modifying the built MD file.

You'll have to update the link in packages/i18n/src/sprintf.js#L23.

[lephleg]

@talldan thanks for the assistance! I tried the npm run docs:build command but all it does is reverting my changes back to the original. That's the reason the static analysis is failing after running the above command. It's not clear to me yet why this is happening though.
Following @mkaz's extended guide along with the documentation Contributor's Guide I find no reference to additional steps required in order to update an existing document. I'll have to dig in to the build script itself.

It's because you are modifying the built MD file.

You'll have to update the link in packages/i18n/src/sprintf.js#L23.

Oh damn, I didn't realise that was generated. Thanks for the guidance @swissspidy! Clean-pushed now.

[talldan]

Thanks for working on this @lephleg

[github-actions]

Congratulations on your first merged pull request, @lephleg! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts:

https://profiles.wordpress.org/me/profile/edit/

And if you don't have a WordPress.org account, you can create one on this page:

https://login.wordpress.org/register

Kudos!