Welcome to the third edition of the Pro Git book.
You can find this book online at: https://git-scm.com/book
Like the previous editions, the third 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; here’s an AsciiDoc quick reference.
We’ve also moved to keeping the translations in separate repositories rather than subdirectories of the English repository. See the translating document for more information.
You can generate the e-book files manually with Asciidoctor. If you run the following you may actually get HTML, Epub, Mobi and PDF output files:
$ bundle install $ bundle exec rake book:build Converting to HTML... -- HTML output at progit.html Converting to EPub... -- Epub output at progit.epub Converting to Mobi (kf8)... -- Mobi output at progit.mobi Converting to PDF... -- PDF output at progit.pdf
You can generate just one of the supported formats (HTML, EPUB, mobi, or PDF). Use one of the following commands:
To generate the HTML book:
$ bundle exec rake book:build_html
To generate the EPUB book:
$ bundle exec rake book:build_epub
To generate the mobi book:
$ bundle exec rake book:build_mobi
To generate the PDF book:
$ bundle exec rake book:build_pdf
As an alternative to the Rake tasks, this repository ships a small,
dependency-free Rust build tool in the builder/ directory.
It drives the same Asciidoctor toolchain but gives you a single command for
every format, and can serve the book as a multi-page reader on a local web
server — one page per section with a sidebar and prev/next navigation, like
the online book.
$ cargo build --release --manifest-path builder/Cargo.toml $ ./builder/target/release/progit all # HTML, PDF, EPUB and Mobi $ ./builder/target/release/progit pdf # just one format $ ./builder/target/release/progit serve --open # read it locally in a browser
See the builder README for the full list of commands and options.
Before signaling an issue, please check that there isn’t already a similar one in the bug tracking system.
Also, if this issue has been spotted on the git-scm.com site, please cross-check that it is still present in this repo. The issue may have already been corrected, but the changes have not been deployed yet.
If you’d like to help out by making a change, take a look at the contributor’s guide.