mirrors/conventionalcommits.org
0
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2025-08-23 06:18:38 +00:00
Code

Docs: Add clarification on commit type casing

Browse Source 
Resolves #24
This commit is contained in:
Jonathan Chen 2018-08-20 07:47:01 -07:00 committed by Damiano Petrungaro
parent ff3ce880b8
commit 369a1d4795
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
index.md
View File

@ -116,6 +116,10 @@ The description is a short description of the code changes, e.g., _fix: array pa
We recommend that you proceed as if you've an already released product. Typically *somebody*, even if its your fellow software developers, is using your software. They'll want to know what's fixed, what breaks etc. We recommend that you proceed as if you've an already released product. Typically *somebody*, even if its your fellow software developers, is using your software. They'll want to know what's fixed, what breaks etc.
### Are the types in the commit title uppercase or lowercase?
Any casing may be used, but it's best to be consistent.
### What do I do if the commit conforms to more than one of the commit types? ### What do I do if the commit conforms to more than one of the commit types?
Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs. Go back and make multiple commits whenever possible. Part of the benefit of Conventional Commits is its ability to drive us to make more organized commits and PRs.