Update link redirects (#1002)

Author: hugovk

documentation/translating.rst

@@ -103,7 +103,7 @@ in production; others are works in progress.
 .. _github_ar: https://github.com/Abdur-rahmaanJ/python-docs-ar
 .. _github_bn_in: https://github.com/python/python-docs-bn-in
 .. _github_es: https://github.com/python/python-docs-es
-.. _github_fa: https://github.com/mmdbalkhi/python-docs-fa
+.. _github_fa: https://github.com/ftg-iran/python-docs-fa
 .. _github_fr: https://github.com/python/python-docs-fr
 .. _github_hi_in: https://github.com/CuriousLearner/python-docs-hi-in
 .. _github_hu: https://github.com/python/python-docs-hu
@@ -122,9 +122,9 @@ in production; others are works in progress.
 .. _mail_lt: https://mail.python.org/pipermail/doc-sig/2019-July/004138.html
 .. _mail_pl: https://mail.python.org/pipermail/doc-sig/2019-April/004106.html
 .. _mail_ru: https://mail.python.org/pipermail/doc-sig/2019-May/004131.html
-.. _tx_pl: https://www.transifex.com/python-doc/python-newest/
-.. _tx_uk: https://www.transifex.com/python-doc/python-newest/
-.. _tx_zh_cn: https://www.transifex.com/python-doc/python-newest/
+.. _tx_pl: https://explore.transifex.com/python-doc/python-newest/
+.. _tx_uk: https://explore.transifex.com/python-doc/python-newest/
+.. _tx_zh_cn: https://explore.transifex.com/python-doc/python-newest/
 .. _wiki_pt_br: https://python.org.br/traducao/
 
 Starting a new translation

getting-started/git-boot-camp.rst

@@ -373,8 +373,8 @@ you run ``git merge upstream/main``.
 
 When it happens, you need to resolve conflict.  See these articles about resolving conflicts:
 
-- `About merge conflicts <https://help.github.com/en/articles/about-merge-conflicts>`_
-- `Resolving a merge conflict using the command line <https://help.github.com/en/articles/resolving-a-merge-conflict-using-the-command-line>`_
+- `About merge conflicts <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts>`_
+- `Resolving a merge conflict using the command line <https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line>`_
 
 .. _git_from_patch:
 
@@ -552,7 +552,7 @@ prior to merging themselves, rather than asking the submitter to do them. This
 can be particularly appropriate when the remaining changes are bookkeeping
 items like updating ``Misc/ACKS``.
 
-.. _Allow edits from maintainers: https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/
+.. _Allow edits from maintainers: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork
 
 To edit an open pull request that targets ``main``:
 

getting-started/pull-request-lifecycle.rst

@@ -64,8 +64,8 @@ Here is a quick overview of how you can contribute to CPython:
 .. _create an issue: https://github.com/python/cpython/issues
 .. _CPython: https://github.com/python/cpython
 .. _use HTTPS: https://help.github.com/articles/which-remote-url-should-i-use/
-.. _Create Pull Request: https://help.github.com/articles/creating-a-pull-request/
-.. _comments on your Pull Request: https://help.github.com/articles/commenting-on-a-pull-request/
+.. _Create Pull Request: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
+.. _comments on your Pull Request: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request
 
 
 .. _pullrequest-steps:
@@ -363,7 +363,7 @@ This will get your changes up to GitHub.
 
 Now you want to
 `create a pull request from your fork
-<https://help.github.com/articles/creating-a-pull-request-from-a-fork/>`_.
+<https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork>`_.
 If this is a pull request in response to a pre-existing issue on the
 `issue tracker`_, please make sure to reference the issue number using
 ``gh-NNNNN:`` prefix in the pull request title and ``#NNNNN`` in the description.
@@ -398,7 +398,7 @@ existing patch. In this case, both parties should sign the :ref:`CLA <cla>`.
 When creating a pull request based on another person's patch, provide
 attribution to the original patch author by adding "Co-authored-by:
 Author Name <email_address> ." to the pull request description and commit message.
-See `the GitHub article <https://help.github.com/articles/creating-a-commit-with-multiple-authors/>`_
+See `the GitHub article <https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors>`_
 on how to properly add the co-author info.
 
 See also :ref:`Applying a Patch to Git <git_from_patch>`.

getting-started/setup-building.rst

@@ -44,7 +44,7 @@ itself. git is easily available for all common operating systems.
 - **Configure**
 
   Configure :ref:`your name and email <set-up-name-email>` and create
-  `an SSH key <https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/>`_
+  `an SSH key <https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account>`_
   as this will allow you to interact with GitHub without typing a username
   and password each time you execute a command, such as ``git pull``,
   ``git push``, or ``git fetch``.  On Windows, you should also

index.rst

@@ -183,8 +183,6 @@ Key Resources
     * :PEP:`7` (Style Guide for C Code)
     * :PEP:`8` (Style Guide for Python Code)
 * `Issue tracker`_
-    * `Meta tracker <https://issues.roundup-tracker.org/>`_ (issue
-      tracker for the issue tracker)
     * :ref:`experts`
 * `Buildbot status`_
 * Source code

internals/compiler.rst

@@ -690,7 +690,7 @@ References
    (https://legacy.python.org/workshops/1998-11/proceedings/papers/montanaro/montanaro.html)
 
 .. [#Bytecodehacks] Bytecodehacks Project
-   (http://bytecodehacks.sourceforge.net/bch-docs/bch/index.html)
+   (https://bytecodehacks.sourceforge.net/bch-docs/bch/index.html)
 
 .. [#CALL_ATTR] CALL_ATTR opcode
    (https://bugs.python.org/issue709744)

testing/coverage.rst

@@ -292,4 +292,4 @@ about 20 to 30 minutes on a modern computer.
 
 .. _issue tracker: https://github.com/python/cpython/issues
 .. _gcov: https://gcc.gnu.org/onlinedocs/gcc/Gcov.html
-.. _lcov: http://ltp.sourceforge.net/coverage/lcov.php
+.. _lcov: https://ltp.sourceforge.net/coverage/lcov.php

triage/github-bpo-faq.rst

@@ -80,7 +80,7 @@ Add a checkbox list like this in the issue description::
 then those will become sub-tasks on the given issue. Moreover, GitHub will
 automatically mark a task as complete if the other referenced issue is
 closed. More details in the `official GitHub documentation
-<https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists>`_.
+<https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists>`_.
 
 What on Earth is a "mannequin"?
 ===============================

triage/labels.rst

@@ -357,7 +357,7 @@ automatically mark a task as complete if the other referenced issue is
 closed.
 
 More details in the `official GitHub documentation
-<https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists>`_.
+<https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/about-task-lists>`_.
 
 Superseder
 ----------