Git commit schema

[kohlbrr]

We should decide on a schema for our git commit messages (enhancement, bugfix, new feature, etc.)

[kohlbrr]

From Drew:

---

Semantic commits create specific, uniform commits. This allows us to easily track progress in our development, pinpoint when bugs are introduced, and in a worse case scenario identify where we need to roll back code. Semantic commits also encourage smaller, more frequent commits as opposed to committing large chunks of code that may contain numerous changes.

A semantic commit has 3 parts:

• the type of commit (feature, test, fix, style, refactor, etc.)
• the subject of the committed code

• a present-tense description of what the commited code does

  git commit -m 'feature(Cart): cart persists to local storage' git commit -m 'test(Product): tests method defined on product model'