I would be more than happy to have you contribute to this project!
- check the existing issues to see if one matches the change you would like to add
- fork this project
- create a descriptive branch name that starts with your name
- make all changes on this newly created branch
- push this branch to your fork
- submit a pull request
Make sure to follow these conventions:
- Commit message must begin with a
type
prefix. i.e. feat, fix, etc. - Commit message must have a solid subject line that describes the work that was done.
Example of a commit message:
feat: adding in a loading spinner component, displayed during API calls, and component loading.
feat
: a new featurefix
: a bug fixdocs
: changes to documentationstyle
: formatting, missing semi colons, etc; no code changerefactor
: refactoring production codetest
: adding tests, refactoring test; no production code changechore
: updating build tasks, package manager configs, etc; no production code change
Commit message types taken from Udacity's git-style guide. View the style guide at: http://udacity.github.io/git-styleguide/