summaryrefslogtreecommitdiff
path: root/docs/internals/contributing/committing-code.txt
diff options
context:
space:
mode:
authorakki <akki@users.noreply.github.com>2016-11-16 03:30:50 +0530
committerTim Graham <timograham@gmail.com>2016-11-15 17:00:50 -0500
commit74ed20b49ade9f1cbd9af294e35478d8e0f59344 (patch)
tree102d77120cfc313b98ed02a8e9801666255d1725 /docs/internals/contributing/committing-code.txt
parent7c6efb3233ce01db96384483cef47769fba58ce2 (diff)
Replaced "django" with "Django" in spelling_wordlist.
Diffstat (limited to 'docs/internals/contributing/committing-code.txt')
-rw-r--r--docs/internals/contributing/committing-code.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/internals/contributing/committing-code.txt b/docs/internals/contributing/committing-code.txt
index 32be5f1f06..445e341dda 100644
--- a/docs/internals/contributing/committing-code.txt
+++ b/docs/internals/contributing/committing-code.txt
@@ -109,9 +109,9 @@ Committing guidelines
In addition, please follow the following guidelines when committing code to
Django's Git repository:
-* Never change the published history of django/django branches! **Never
- force-push your changes to django/django.** If you absolutely must (for
- security reasons for example) first discuss the situation with the core team.
+* Never change the published history of ``django/django`` branches by force
+ pushing. If you absolutely must (for security reasons for example), first
+ discuss the situation with the team.
* For any medium-to-big changes, where "medium-to-big" is according to
your judgment, please bring things up on the |django-developers|
@@ -242,7 +242,7 @@ When a mistaken commit is discovered, please follow these guidelines:
* The release branch maintainer may back out commits to the release
branch without permission if the commit breaks the release branch.
-* If you mistakenly push a topic branch to django/django, just delete it.
+* If you mistakenly push a topic branch to ``django/django``, just delete it.
For instance, if you did: ``git push upstream feature_antigravity``,
just do a reverse push: ``git push upstream :feature_antigravity``.