59 Making an new branch for each set of related changes will make it easier for

150 Enter a title for the set of changes, and some explanation of what you've done.
151 Say if there is anything you'd like particular attention for - like a

213 There's an embarrassing typo in a commit you made? Or perhaps the you
214 made several false starts you would like the posterity not to see.

282 and the history looks now like this::

317 worry that ``main`` has got a little ahead.  But sometimes, the changes in

352 When all looks good you can delete your backup branch::

393 fail with an error that looks like ::

405 If this push had succeed then the commits ``A``, ``B``, and ``C`` would no
406 longer be referenced by any branch and be discarded:

420 versions from our local branch.  In this case, what we want to do is ::

431 history and if anyone has fetched the old commits will have a different view
432 of history which can cause confusion.