From c34c6d0a2fc6d9bc55fb2db94b9ed40141babb15 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 1 Feb 2019 15:42:48 -0500 Subject: Used extlinks for GitHub commits. --- docs/internals/howto-release-django.txt | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'docs/internals') 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 `). #. 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 -- cgit v1.3