From 01f658644a7ee7cbff4ee5626d5894e9049ee8d5 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 20 May 2017 17:51:21 +0200 Subject: Updated various links in docs to avoid redirects Thanks Tim Graham and Mariusz Felisiak for review and completion. --- docs/internals/contributing/localizing.txt | 2 +- docs/internals/contributing/writing-code/unit-tests.txt | 4 ++-- docs/internals/contributing/writing-code/working-with-git.txt | 4 ++-- docs/internals/contributing/writing-documentation.txt | 2 +- docs/internals/git.txt | 4 ++-- docs/internals/howto-release-django.txt | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-) (limited to 'docs/internals') diff --git a/docs/internals/contributing/localizing.txt b/docs/internals/contributing/localizing.txt index e3df902549..f0d89f9001 100644 --- a/docs/internals/contributing/localizing.txt +++ b/docs/internals/contributing/localizing.txt @@ -70,7 +70,7 @@ Django source tree, as for any code change: .. _Transifex: https://www.transifex.com/ .. _Django project page: https://www.transifex.com/django/django/ -.. _Transifex User Guide: http://docs.transifex.com/ +.. _Transifex User Guide: https://docs.transifex.com/ .. _translating-documentation: diff --git a/docs/internals/contributing/writing-code/unit-tests.txt b/docs/internals/contributing/writing-code/unit-tests.txt index 74ec363b5a..6dbbf06518 100644 --- a/docs/internals/contributing/writing-code/unit-tests.txt +++ b/docs/internals/contributing/writing-code/unit-tests.txt @@ -60,7 +60,7 @@ Having problems? See :ref:`troubleshooting-unit-tests` for some common issues. Running tests using ``tox`` --------------------------- -`Tox `_ is a tool for running tests in different +`Tox `_ is a tool for running tests in different virtual environments. Django includes a basic ``tox.ini`` that automates some checks that our build server performs on pull requests. To run the unit tests and other checks (such as :ref:`import sorting `, the @@ -272,7 +272,7 @@ associated tests will be skipped. .. _gettext: https://www.gnu.org/software/gettext/manual/gettext.html .. _selenium: https://pypi.python.org/pypi/selenium .. _sqlparse: https://pypi.python.org/pypi/sqlparse -.. _pip requirements files: https://pip.pypa.io/en/latest/user_guide.html#requirements-files +.. _pip requirements files: https://pip.pypa.io/en/latest/user_guide/#requirements-files Code coverage ------------- diff --git a/docs/internals/contributing/writing-code/working-with-git.txt b/docs/internals/contributing/writing-code/working-with-git.txt index 85ca6dfc85..1ace449189 100644 --- a/docs/internals/contributing/writing-code/working-with-git.txt +++ b/docs/internals/contributing/writing-code/working-with-git.txt @@ -18,7 +18,7 @@ Installing Git ============== Django uses `Git`_ for its source control. You can `download -`_ Git, but it's often easier to install with +`_ Git, but it's often easier to install with your operating system's package manager. Django's `Git repository`_ is hosted on `GitHub`_, and it is recommended @@ -34,7 +34,7 @@ Note that ``user.name`` should be your real name, not your GitHub nick. GitHub should know the email you use in the ``user.email`` field, as this will be used to associate your commits with your GitHub account. -.. _Git: http://git-scm.com/ +.. _Git: https://git-scm.com/ .. _Git repository: https://github.com/django/django/ .. _GitHub: https://github.com/ diff --git a/docs/internals/contributing/writing-documentation.txt b/docs/internals/contributing/writing-documentation.txt index e19b5854fd..d58c318408 100644 --- a/docs/internals/contributing/writing-documentation.txt +++ b/docs/internals/contributing/writing-documentation.txt @@ -427,7 +427,7 @@ Before you commit your docs, it's a good idea to run the spelling checker. You'll need to install a couple packages first: * `pyenchant `_ (which requires - `enchant `_) + `enchant `_) * `sphinxcontrib-spelling `_ diff --git a/docs/internals/git.txt b/docs/internals/git.txt index 386a2a05a7..f71c1e921d 100644 --- a/docs/internals/git.txt +++ b/docs/internals/git.txt @@ -52,8 +52,8 @@ The source code for the `Djangoproject.com `_ website can be found at `github.com/django/djangoproject.com `_. -.. _Git: http://git-scm.com/ -.. _documentation: http://git-scm.com/documentation +.. _Git: https://git-scm.com/ +.. _documentation: https://git-scm.com/documentation .. _branches: https://github.com/django/django/branches .. _tags: https://github.com/django/django/tags diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt index bfa42614ef..495b7217b5 100644 --- a/docs/internals/howto-release-django.txt +++ b/docs/internals/howto-release-django.txt @@ -155,7 +155,7 @@ OK, this is the fun part, where we actually push out a release! #. Check `Jenkins`__ is green for the version(s) you're putting out. You probably shouldn't issue a release until it's green. - __ http://djangoci.com + __ https://djangoci.com #. A release always begins from a release branch, so you should make sure you're on a stable branch and up-to-date. For example:: -- cgit v1.3