diff --git a/docs/internals/contributing/committing-code.txt b/docs/internals/contributing/committing-code.txt
index e33269b..e2d6422 100644
a
|
b
|
repository:
|
49 | 49 | immediately, so you may have to wait a couple of days before getting a |
50 | 50 | response. |
51 | 51 | |
52 | | * Write detailed commit messages in the past tense, not present tense. |
| 52 | * When you write detailed commit messages, use this pattern:: |
53 | 53 | |
54 | | * Good: "Fixed Unicode bug in RSS API." |
55 | | * Bad: "Fixes Unicode bug in RSS API." |
56 | | * Bad: "Fixing Unicode bug in RSS API." |
| 54 | [<Django version>] Fixed <ticket> -- <description> Backport of <revision> |
| 55 | |
| 56 | For example:: |
| 57 | |
| 58 | [1.3.X] Fixed #17028 - Changed diveintopython.org -> diveintopython.net. Backport of r17115. |
| 59 | |
| 60 | Note that description was written in the past tense. The following one |
| 61 | is not correct:: |
| 62 | |
| 63 | [1.3.X] Fixed #17028 - Changing diveintopython.org -> diveintopython.net. Backport of r17115. |
57 | 64 | |
58 | 65 | * For commits to a branch, prefix the commit message with the branch name. |
59 | 66 | For example: "magic-removal: Added support for mind reading." |