Skip to content

Commit fcdd9de

Browse files
jeff5ncoghlan
authored andcommitted
Demote "Working with Git" within committing.rst (python#285)
Makes committing.rst consistent with the rest of the guide in having just one top-level section. This eliminates a surprise navigation where 18 comes next after 16.
1 parent 4f8835a commit fcdd9de

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

committing.rst

+4-4
Original file line numberDiff line numberDiff line change
@@ -193,7 +193,7 @@ unprocessed.)
193193

194194

195195
Working with Git_
196-
=================
196+
-----------------
197197

198198
.. seealso::
199199
:ref:`gitbootcamp`
@@ -226,7 +226,7 @@ clone gets into a state you aren't happy with.
226226
.. _committing-active-branches:
227227

228228
Active branches
229-
---------------
229+
'''''''''''''''
230230

231231
If you do ``git branch`` you will see a :ref:`list of branches <listbranch>`.
232232
``master`` is the in-development branch, and is the only branch that receives
@@ -236,7 +236,7 @@ new features. The other branches only receive bug fixes or security fixes.
236236
.. _branch-merge:
237237

238238
Backporting Changes to an Older Version
239-
---------------------------------------
239+
'''''''''''''''''''''''''''''''''''''''
240240

241241
When it is determined that a pull request needs to be backported into one or
242242
more of the maintenance branches, a core developer can apply the labels
@@ -266,7 +266,7 @@ Developers can apply labels to GitHub pull requests).
266266

267267

268268
Reverting a Merged Pull Request
269-
-------------------------------
269+
'''''''''''''''''''''''''''''''
270270

271271
To revert a merged pull request, press the ``Revert`` button at the bottom of
272272
the pull request. It will bring up the page to create a new pull request where

0 commit comments

Comments
 (0)