Skip to content

Commit

Permalink
πŸ› FIX: Readme Typos (#4)
Browse files Browse the repository at this point in the history
  • Loading branch information
theodesp authored and Ahmad Awais ⚑️ committed Oct 1, 2018
1 parent 9655173 commit e789072
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,29 +39,29 @@ I like emoji. I like ’em a lot. Programming, code, geeks/nerds, open source, a

Only use the following Git Commit Messages. Simple and small foot print is the key here.

1. `πŸ“¦ NEW: IMPERITIVE_MESSAGE_GOES_HERE`
1. `πŸ“¦ NEW: IMPERATIVE_MESSAGE_GOES_HERE`
> Use when you add something completely new.
> E.g. `πŸ“¦ NEW: Add Git ignore file`

1. `πŸ‘Œ IMPROVE: IMPERITIVE_MESSAGE_GOES_HERE`
1. `πŸ‘Œ IMPROVE: IMPERATIVE_MESSAGE_GOES_HERE`
> Use when you improve/enhance piece of code like refactoring etc.
> E.g. `πŸ‘Œ IMPROVE: Remote IP API Function`

1. `πŸ› FIX: IMPERITIVE_MESSAGE_GOES_HERE`
1. `πŸ› FIX: IMPERATIVE_MESSAGE_GOES_HERE`
> Use when you fix a bug β€” need I say more?
> E.g. `πŸ› FIX: Case convertor`

1. `πŸ“– DOC: IMPERITIVE_MESSAGE_GOES_HERE`
1. `πŸ“– DOC: IMPERATIVE_MESSAGE_GOES_HERE`
> Use when you add documentation like `README.md`, or even inline docs.
> E.g. `πŸ“– DOC: API Interface Tutorial`


1. `πŸš€ RELEASE: IMPERITIVE_MESSAGE_GOES_HERE`
1. `πŸš€ RELEASE: IMPERATIVE_MESSAGE_GOES_HERE`
> Use when you release a new version.
> E.g. `πŸš€ RELEASE: Version 2.0.0`


1. `βœ… TEST: IMPERITIVE_MESSAGE_GOES_HERE`
1. `βœ… TEST: IMPERATIVE_MESSAGE_GOES_HERE`
> Use when you release a new version.
> E.g. `βœ… TEST: Mock User Login/Logout`

Expand Down

0 comments on commit e789072

Please sign in to comment.