Feat: custom type (closes #31)

[JPeer264]

(ref: #31)

[coveralls]

Coverage decreased (-0.5%) to 99.531% when pulling 862f9a9 on feat/ustom-type into 54ea475 on master.

[coveralls]

Coverage remained the same at 100.0% when pulling af2d0d4 on feat/ustom-type into c14a9c3 on master.

[yordis]

I would do feat(TICKET-NUMBER) ... instead of creating new types for this.

[JPeer264]

@yordis this is actually already implemented as scope

[JPeer264]

Actually what you suggested works too and is also imo much better to read. Unfortunately different companies have different rules - and e.g.: PRE-21: this is a new commit is one of them

[yordis]

@JPeer264 but then people can't assume the tags and other things from the type of the commit.

For the most part, that information is random metadata that you can't rely on.

This is why I think is better to put it as scope (since they kind of are)

[JPeer264]

I agree to 100% on this.

But still there are projects where this needs to be done (as some of the projects I am working on have this kinda rule). I guess I'll append your suggested method to the readme as well.

[aichbauer]

LGTM