summaryrefslogtreecommitdiff
path: root/docs/internals
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2019-02-01 15:42:48 -0500
committerCarlton Gibson <carlton.gibson@noumenal.es>2019-02-01 21:42:48 +0100
commitc34c6d0a2fc6d9bc55fb2db94b9ed40141babb15 (patch)
tree46fd1d7ab5477579c2399136daed8e0451225038 /docs/internals
parent75d627888bf42f8de6064a0bd665c98c0df66c55 (diff)
Used extlinks for GitHub commits.
Diffstat (limited to 'docs/internals')
-rw-r--r--docs/internals/howto-release-django.txt4
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/internals/howto-release-django.txt b/docs/internals/howto-release-django.txt
index 6f91751616..730196223d 100644
--- a/docs/internals/howto-release-django.txt
+++ b/docs/internals/howto-release-django.txt
@@ -179,9 +179,7 @@ OK, this is the fun part, where we actually push out a release!
checkout security/1.5.x; git rebase stable/1.5.x``) and then switch back and
do the merge. Make sure the commit message for each security fix explains
that the commit is a security fix and that an announcement will follow
- (`example security commit`__).
-
- __ https://github.com/django/django/commit/3ef4bbf495cc6c061789132e3d50a8231a89406b
+ (:commit:`example security commit <bf39978a53f117ca02e9a0c78b76664a41a54745>`).
#. For a feature release, remove the ``UNDER DEVELOPMENT`` header at the
top of the release notes and add the release date on the next line. For a