You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
# The bluejava Git Commit Message Format Guide
2
-
*Version 0.5.0*
2
+
*Version 0.5.1*
3
3
4
4
This is a guide to creating better Git commit messages. By following this guide, you and/or your team will create a more consistent and consistently useful change log.
5
5
@@ -119,7 +119,7 @@ Often a change will include more than one type. Use the type highest on this lis
119
119
120
120
For example, a new feature (FEAT type) will often also include new documentation (DOCS) and tests (TEST). In this case, simply state the type as **FEAT**.
121
121
122
-
If the change is a bugfix (FIX) that required some refactoring (REFACTOR), that is less obvious and probably helpful to be stated as a multi-type change, **FIX/REFACTOR**.
122
+
If the change is a bugfix (FIX) that required changes to the build script (MAINT), that is less obvious and probably helpful to be stated as a multi-type change, **FIX/MAINT**.
123
123
124
124
Note the relationship between various *types* of commits and the expectation of a corresponding change in [Semantic Versioning (SemVer)](http://semver.org) version number:
125
125
@@ -169,4 +169,4 @@ MAINT: add bower.json
169
169
170
170
Here is a little image you can drag to your desktop and popup whenever you are making a change commit:
0 commit comments