How to contribute?
First, welcome to Ace and thank you so much for willing to contribute!
Submitting an issue
Feel free to file issues on our GitHub issue tracker.
When filing an issue, please provide the following details:
- the version of Ace impacted by the issue (it can be retrieved by running
ace -vin a command shell).
- the version of Node used to run Ace (it can be retrieved by running
node -vin a command shell).
- if possible, provide the error details as produced in the error log
We accept changes via GitHub pull requests.
We try to keep a clean and readable commit history, so if we decide to merge your code we will rebase your commits on the
master branch, and possibly squash them too.
Please make sure your branch is reasonably up-to-date with the
master branch (by regularly pulling from or rebasing onto the
Please make surre to provided tests for any change you’re proposing.
We do not yet have formal code style guidelines, so please try to respect the style of the code files you are editting!
We may change your code style when merging a pull request.
We follow a commit message convention (adapted from Angular’s convention), which allows us to keep a readable history and automatically generate change logs.
Each commit message should consist of a simple header, a body, and an optional footer, each separated with a blank line. The header is a single line consisting of a type, an optional scope, and a subject.
The allowed types are:
- feat (feature)
- fix (bug fix)
- docs (documentation)
- style (formatting, missing semi colons, …)
- test (when adding missing tests)
- chore (maintain)
An example of a commit message is
feat: enable support for checking EPUB 2.0.1 - Make sure that the parsing doesn’t choke on EPUB 2.0.1 - Warn when checking an EPUB 2.0.1 Closes #21