We'd love for you to contribute to our source code and to make angular-gantt better !

Source code is available on GitHub under the MIT License. You may also read Sources section to learn how to build angular-gantt from sources.

Here are the guidelines we'd like you to follow:

Issues Guidelines

Before you submit your issue search the archive, maybe your question was already answered.

If you didn't found anything related in the archive, you can create a new issue providing:

Coding Rules

Branching Guidelines

Pull Request Guidelines

Git Commit Guidelines

This commit guidelines is inspired by angularJS project.

We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the AngularJS change log.

Commit Message Format

Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:

<type>(<scope>): <subject>

Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on github as well as in various git tools.


Must be one of the following:


The scope could be anything specifying place of the commit change. For example row, task, header, options, css, readme, etc...


The subject contains succinct description of the change:


Just as in the subject, use the imperative, present tense: "change" not "changed" nor "changes" The body should include the motivation for the change and contrast this with previous behavior.

The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues that this commit Closes.

A detailed explanation can be found in this document.