From 369a1d4795982cd707a1e74b991ff898b0abb2cf Mon Sep 17 00:00:00 2001 From: Jonathan Chen Date: Mon, 20 Aug 2018 07:47:01 -0700 Subject: [PATCH] Docs: Add clarification on commit type casing Resolves #24 --- index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/index.md b/index.md index 105a62b..9d6de09 100644 --- a/index.md +++ b/index.md @@ -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. +### 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? 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.