Refs #32720 -- Updated various links in docs to avoid redirects and use HTTPS.

This commit is contained in:
Nick Pope 2021-04-27 12:09:00 +01:00 committed by Mariusz Felisiak
parent 7c4ee487c7
commit c156e36955
55 changed files with 100 additions and 97 deletions

View file

@ -138,7 +138,7 @@ Django's Git repository:
Credit the contributors in the commit message: "Thanks A for the report and B
for review." Use git's `Co-Authored-By`_ as appropriate.
.. _Co-Authored-By: https://help.github.com/articles/creating-a-commit-with-multiple-authors/
.. _Co-Authored-By: https://docs.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors
* For commits to a branch, prefix the commit message with the branch name.
For example: "[1.4.x] Fixed #xxxxx -- Added support for mind reading."

View file

@ -142,7 +142,7 @@ Running tests using ``django-docker-box``
supported databases and python versions. See the `django-docker-box`_ project
page for installation and usage instructions.
.. _django-docker-box: https://github.com/django/django-docker-box
.. _django-docker-box: https://github.com/django/django-docker-box/
.. _running-unit-tests-settings:
@ -320,13 +320,13 @@ associated tests will be skipped.
To run some of the autoreload tests, you'll need to install the Watchman_
service.
.. _argon2-cffi: https://pypi.org/project/argon2_cffi/
.. _argon2-cffi: https://pypi.org/project/argon2-cffi/
.. _asgiref: https://pypi.org/project/asgiref/
.. _bcrypt: https://pypi.org/project/bcrypt/
.. _colorama: https://pypi.org/project/colorama/
.. _docutils: https://pypi.org/project/docutils/
.. _geoip2: https://pypi.org/project/geoip2/
.. _jinja2: https://pypi.org/project/jinja2/
.. _jinja2: https://pypi.org/project/Jinja2/
.. _numpy: https://pypi.org/project/numpy/
.. _Pillow: https://pypi.org/project/Pillow/
.. _PyYAML: https://pyyaml.org/wiki/PyYAML

View file

@ -61,7 +61,7 @@ To get started contributing, you'll want to read the :ref:`reStructuredText
reference <sphinx:rst-index>`.
Your locally-built documentation will be themed differently than the
documentation at `docs.djangoproject.com <https://docs.djangoproject.com>`_.
documentation at `docs.djangoproject.com <https://docs.djangoproject.com/>`_.
This is OK! If your changes look good on your local machine, they'll look good
on the website.

View file

@ -50,7 +50,7 @@ website can be found at `github.com/django/djangoproject.com
<https://github.com/django/djangoproject.com>`_.
.. _Git: https://git-scm.com/
.. _documentation: https://git-scm.com/documentation
.. _documentation: https://git-scm.com/doc
.. _branches: https://github.com/django/django/branches
.. _tags: https://github.com/django/django/tags

View file

@ -337,7 +337,7 @@ Now you're ready to actually put the release out there. To do this:
that they install correctly, but it'll catch silly mistakes.
#. Ask a few people on IRC to verify the checksums by visiting the checksums
file (e.g. https://www.djangoproject.com/m/pgp/Django-1.5b1.checksum.txt)
file (e.g. https://media.djangoproject.com/pgp/Django-1.5b1.checksum.txt)
and following the instructions in it. For bonus points, they can also unpack
the downloaded release tarball and verify that its contents appear to be
correct (proper version numbers, no stray ``.pyc`` or other undesirable
@ -451,8 +451,8 @@ need to be done by the releaser.
<https://readthedocs.org/projects/django/>`_. Since the automatically
generated version names ("stable-A.B.x") differ from the version names
used in Read the Docs ("A.B.x"), `create a ticket
<https://github.com/rtfd/readthedocs.org/issues/5537>`_ requesting the new
version.
<https://github.com/readthedocs/readthedocs.org/issues/5537>`_ requesting
the new version.
#. `Request the new classifier on PyPI
<https://github.com/pypa/trove-classifiers/issues/29>`_. For example

View file

@ -31,7 +31,7 @@ installation, usage, or debugging of Django.
* `django-users subscription email address`_
* `django-users posting email`_
.. _django-users mailing archive: https://groups.google.com/d/forum/django-users
.. _django-users mailing archive: https://groups.google.com/g/django-users
.. _django-users subscription email address: mailto:django-users+subscribe@googlegroups.com
.. _django-users posting email: mailto:django-users@googlegroups.com
@ -48,7 +48,7 @@ the Django Project.
* `django-core-mentorship subscription email address`_
* `django-core-mentorship posting email`_
.. _django-core-mentorship mailing archive: https://groups.google.com/d/forum/django-core-mentorship
.. _django-core-mentorship mailing archive: https://groups.google.com/g/django-core-mentorship
.. _django-core-mentorship subscription email address: mailto:django-core-mentorship+subscribe@googlegroups.com
.. _django-core-mentorship posting email: mailto:django-core-mentorship@googlegroups.com
@ -73,7 +73,7 @@ answered there.
* `django-developers subscription email address`_
* `django-developers posting email`_
.. _django-developers mailing archive: https://groups.google.com/d/forum/django-developers
.. _django-developers mailing archive: https://groups.google.com/g/django-developers
.. _django-developers subscription email address: mailto:django-developers+subscribe@googlegroups.com
.. _django-developers posting email: mailto:django-developers@googlegroups.com
@ -89,7 +89,7 @@ Django's components.
* `django-i18n subscription email address`_
* `django-i18n posting email`_
.. _django-i18n mailing archive: https://groups.google.com/d/forum/django-i18n
.. _django-i18n mailing archive: https://groups.google.com/g/django-i18n
.. _django-i18n subscription email address: mailto:django-i18n+subscribe@googlegroups.com
.. _django-i18n posting email: mailto:django-i18n@googlegroups.com
@ -105,7 +105,7 @@ A (very) low-traffic list for announcing :ref:`upcoming security releases
* `django-announce subscription email address`_
* `django-announce posting email`_
.. _django-announce mailing archive: https://groups.google.com/d/forum/django-announce
.. _django-announce mailing archive: https://groups.google.com/g/django-announce
.. _django-announce subscription email address: mailto:django-announce+subscribe@googlegroups.com
.. _django-announce posting email: mailto:django-announce@googlegroups.com
@ -121,6 +121,6 @@ by developers and interested community members.
* `django-updates subscription email address`_
* `django-updates posting email`_
.. _django-updates mailing archive: https://groups.google.com/d/forum/django-updates
.. _django-updates mailing archive: https://groups.google.com/g/django-updates
.. _django-updates subscription email address: mailto:django-updates+subscribe@googlegroups.com
.. _django-updates posting email: mailto:django-updates@googlegroups.com