cchitsiang · March 20, 2016 18:04 · Mar 14, 2016 · Mar 13, 2016 · Mar 4, 2016 · Mar 2, 2016
diff --git a/.git-commit-template.txt b/.git-commit-template.txt
@@ -10,21 +10,19 @@
 
 # --- COMMIT END ---
 # Type can be 
-#    feat (new feature)
-#    fix (bug fix)
-#    docs (changes to documentation)
-#    style (formatting, missing semi colons, etc; no code change)
+#    feat     (new feature)
+#    fix      (bug fix)
 #    refactor (refactoring production code)
-#    test (adding missing tests, refactoring tests; no production code change)
-#    chore (updating grunt tasks etc; no production code change)
+#    style    (formatting, missing semi colons, etc; no code change)
+#    docs     (changes to documentation)
+#    test     (adding or refactoring tests; no production code change)
+#    chore    (updating grunt tasks etc; no production code change)
 # --------------------
 # Remember to
-#    Separate subject from body with a blank line
-#    Limit the subject line to 50 characters
 #    Capitalize the subject line
-#    Do not end the subject line with a period
 #    Use the imperative mood in the subject line
-#    Wrap the body at 72 characters
+#    Do not end the subject line with a period
+#    Separate subject from body with a blank line
 #    Use the body to explain what and why vs. how
 #    Can use multiple lines with "-" for bullet points in body
 # --------------------

diff --git a/.git-commit-template.txt b/.git-commit-template.txt
@@ -1,7 +1,9 @@
 # <type>: (If applied, this commit will...) <subject> (Max 50 char)
+# |<----  Using a Maximum Of 50 Characters  ---->|
 
 
 # Explain why this change is being made
+# |<----   Try To Limit Each Line to a Maximum Of 72 Characters   ---->|
 
 # Provide links or keys to any relevant tickets, articles or other resources
 # Example: Github issue #23
@@ -26,5 +28,5 @@
 #    Use the body to explain what and why vs. how
 #    Can use multiple lines with "-" for bullet points in body
 # --------------------
-# For a full example of how to write a good commit message, check out
-# https://github.com/sparkbox/how_to/tree/master/style/git
+# For more information about this template, check out
+# https://gist.github.com/adeekshith/cd4c95a064977cdc6c50
diff --git a/.git-commit-template.txt b/.git-commit-template.txt
@@ -1,27 +1,30 @@
-# Type(<scope>): <subject>
+# <type>: (If applied, this commit will...) <subject> (Max 50 char)
 
-# <body>
 
-# <footer>
+# Explain why this change is being made
 
-# Type should be one of the following:
-# * feat (new feature)
-# * fix (bug fix)
-# * docs (changes to documentation)
-# * style (formatting, missing semi colons, etc; no code change)
-# * refactor (refactoring production code)
-# * test (adding missing tests, refactoring tests; no production code change)
-# * chore (updating grunt tasks etc; no production code change)
-# Scope is just the scope of the change. Something like (admin) or (teacher).
-# Subject should use impertivite tone and say what you did.
-# The body should go into detail about changes made.
-# The footer should contain any JIRA (or other tool) issue references or actions.
+# Provide links or keys to any relevant tickets, articles or other resources
+# Example: Github issue #23
 
+# --- COMMIT END ---
+# Type can be 
+#    feat (new feature)
+#    fix (bug fix)
+#    docs (changes to documentation)
+#    style (formatting, missing semi colons, etc; no code change)
+#    refactor (refactoring production code)
+#    test (adding missing tests, refactoring tests; no production code change)
+#    chore (updating grunt tasks etc; no production code change)
+# --------------------
+# Remember to
+#    Separate subject from body with a blank line
+#    Limit the subject line to 50 characters
+#    Capitalize the subject line
+#    Do not end the subject line with a period
+#    Use the imperative mood in the subject line
+#    Wrap the body at 72 characters
+#    Use the body to explain what and why vs. how
+#    Can use multiple lines with "-" for bullet points in body
+# --------------------
 # For a full example of how to write a good commit message, check out
-# https://github.com/sparkbox/how_to/tree/master/style/git
-
-# ---------------------------------------------------------------------------------
-# Jira Issue Processing
-# ISSUE_KEY #comment This is a comment
-# ISSUE_KEY #done 
-# ---------------------------------------------------------------------------------
+# https://github.com/sparkbox/how_to/tree/master/style/git
diff --git a/.git-commit-template.txt b/.git-commit-template.txt
@@ -1,5 +1,7 @@
 # Type(<scope>): <subject>
+
 # <body>
+
 # <footer>
 
 # Type should be one of the following:

diff --git a/.git-commit-template.txt b/.git-commit-template.txt
@@ -0,0 +1,25 @@
+# Type(<scope>): <subject>
+# <body>
+# <footer>
+
+# Type should be one of the following:
+# * feat (new feature)
+# * fix (bug fix)
+# * docs (changes to documentation)
+# * style (formatting, missing semi colons, etc; no code change)
+# * refactor (refactoring production code)
+# * test (adding missing tests, refactoring tests; no production code change)
+# * chore (updating grunt tasks etc; no production code change)
+# Scope is just the scope of the change. Something like (admin) or (teacher).
+# Subject should use impertivite tone and say what you did.
+# The body should go into detail about changes made.
+# The footer should contain any JIRA (or other tool) issue references or actions.
+
+# For a full example of how to write a good commit message, check out
+# https://github.com/sparkbox/how_to/tree/master/style/git
+
+# ---------------------------------------------------------------------------------
+# Jira Issue Processing
+# ISSUE_KEY #comment This is a comment
+# ISSUE_KEY #done 
+# ---------------------------------------------------------------------------------