Contributing Guidelines

Please follow these guidelines when you are trying to contribue to kiki_did project.

Code formatting

Please refer to the following wiki page.

https://github.com/playkiki/kiki_did/wiki/Formatting

Naming conventions

Please refer to the following wiki page.

https://github.com/playkiki/kiki_did/wiki/Naming-Conventions

Git commit messages

Generally there are two acceptable styles of commit message.

Basically it's based on this site : https://karma-runner.github.io/0.10/dev/git-commit-msg.html

Available types

chore (updating grunt tasks etc; no production code change)
docs(or doc) (changes to documentation)
feat (new feature)
fix (bug fix)
refactor (refactoring production code)
style (formatting, missing semi colons, etc; no code change)
test (adding missing tests, refactoring tests; no production code change)
deps (anything related to dependencies)

Examples

chore: add Oyster build script
doc: explain hat wobble
feat: add beta sequence
fix: remove broken confirmation message
refactor: share logic between 4d3d3d3 and flarhgunnstow
style: convert tabs to spaces
test: ensure Tayne retains clothing
deps: bump dependencies

Pull Requests

When you make a pull request, explain what you did and what has been changed in detail.

Versioning

We are following the SemVer.