A JavaScript library to draw pretty git graphs in the browser.

Project page: http://gitgraphjs.com/

You have different options to start with the library:

• Download the latest release.
• Clone the repo: git clone git://github.com/nicoespeon/gitgraph.js.git.
• Install with Bower: bower install gitgraph.js.

Production files are available under the build/ directory.

You found some nasty bug or have a cool feature request? Just open a new issue.

Please have a look at the Issue Guidelines from Nicolas Gallagher before doing so.

The JavaScript source code is documented with JSDoc.

Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at http://editorconfig.org.

The project uses Grunt with convenient methods for our workflow. It's how we lint our code, run tests, generate documentation, etc. To use it, install the required dependencies as directed and then run the following Grunt commands.

From the command line:

• Install grunt-cli globally with npm install -g grunt-cli.
• Install the necessary local dependencies with npm install.

When completed, you'll be able to run the various Grunt commands provided from the command line.

> Need more information about how to get started with Grunt?

Check source code against JSHint then runs unit tests with Jasmine.

Generate source code documentation into dist/docs/ (not versioned) with JSDoc.

Clean dist/ directory, lint code, output the minified release into dist/gitgraph.min.js and generate the documentation into dist/docs/.

Lint code, output the source and minified releases into build/ and generate the official documentation into docs/.

For a better code experience, this grunt task opens a live server in your favorite browser. This server is automatically reloaded when you save a project file.

Please note that examples/index.html is the default file for testing ;)

We use SemVer as a guideline for our versioning here.

Releases will be numbered with the following format:

<major>.<minor>.<patch>

And constructed with the following guidelines:

• Breaking backward compatibility bumps the <major> (and resets the <minor> and <patch>)
• New additions without breaking backward compatibility bumps the <minor> (and resets the <patch>)
• Bug fixes and misc. changes bumps the <patch>

Nicolas Carlo - @nicoespeon } http://nicoespeon.com

Fabien Bernard - @fabien0102

Copyright (c) 2013 Nicolas CARLO and Fabien BERNARD under the MIT license.

> What does that mean?