Improve documentation links #218
Conversation
per1234
commented
Apr 13, 2022
per1234
commented
- Update links that were relying on redirects
- Configure links to allow localization where available
github.com and wikipedia.org have different localization behaviors depending on the URL. If a language code is specified via the URL, then that language version of the page is loaded, regardless of the language setting of the user's browser or GitHub. For example, this URL will take the user to the English version of the page even if their browser is configured for Chinese: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github If no language code is specified via the URL, then it redirects to the version of the page localized for the user's language preference, where available. For example, if the user has selected "Chinese" as their preferred language in their browser settings, then this URL: https://docs.github.com/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github redirects to: https://docs.github.com/cn/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github
Even though these links were still reaching the intended page, it is best not to rely on redirects continuing to work indefinitely.
per1234
added
topic: documentation
|
Some of the This problem was already happening before the changes proposed here: It was these spurious failures that motivated me to update the redirecting links, with the idea that maybe all the redirects were somehow causing the link check workflow to pass a threshold where anti-DDoS measures kick in on GitHub's documentation servers. Sadly, it does not seem to have helped, but I think the change is beneficial even though it does not fix the problem of the failing link check. As for the issue of the failing links check (unrelated to this PR), this class of problem has resolved itself in other cases. If that does not happen, I can add the 403 status to the markdown-link-check tool's allow list as a workaround. |
If it's an anti-DDoS measure, it would be possible to have a retry mechanism or a "delay" one? |
