Welcome to the second edition of the Pro Git book.

You can find this book online at: http://git-scm.com/book

Like the first edition, the second edition of Pro Git is open source under a Creative Commons license.

A couple of things have changed since open sourcing the first edition. For one, we’ve moved from Markdown to the amazing Asciidoc format for the text of the book. We’ve also moved to using O’Reilly’s Atlas platform for generating continuous builds of the book so all major formats are always available in every language.

We’ve also moved to keeping the translations in seperate repositories rather than subdirectories of the English repository. See the Translations section for more information.

To contribute errata or new content to this repository, you will need to open up a Pull Request on GitHub. It is generally a good idea before doing anything major to open an issue and make sure your work will get accepted.

Errata and basic clarifications will be accepted if we agree that they improve the content. You can also open an issue so we can figure out how or if it needs to be addressed.

Please refrain from making sweeping copy edit changes as they tend to not get accepted and we don’t want you wasting your time. These changes tend to be very subjective, often only clarifying things for some small percentage of people and it’s rarely worth the time to accept them. Professional copy editors have already reviewed this content multiple times so while you may have somewhat better taste and grammar than we do it’s unlikely that your prose is going to be so much better that it’s worth changing vast swaths of text.

There are two ways to generate e-book content from this source code.

The easiest way is simply to let us do it. A robot is standing by to look for new work on the main branch and automatically build it for everyone.

You can find the current builds on http://git-scm.com/book and more information about the builds available at https://progit.org.

The other way to generate e-book files is to do so manually with Asciidoctor. If you run the following you may actually get HTML, Epub, Mobi and PDF output files:

This uses the asciidoctor, asciidoctor-pdf and asciidoctor-epub projects.

Translations to other languages are highly encouraged but handled a little differently than the first edition. We now keep each translation in a seperate repository and automatically build the output files through Atlas. This was something that was really difficult in the last edition.

Since each translation is a different repository, we can also have different maintainers for each project. The Pro Git team simply pulls them in and builds them for the translation teams. To get automatic builds, translations repositories will have to be under the progit organization on GitHub.

You can find out information on all the current translations and information on how to start your own at: http://progit.org/translations.

The images in this book were generated using Sketch 3, with the included sketchbook file.

To add a figure:

1. Add a page to the sketchbook. Try to use the included symbols wherever possible.

2. Add a ``slice'' to your page. Give it a name that matches the destination PNG filename, relative from the root of the source directory.

3. Make sure your slice is set to export at 3x size.