Permalink
Browse files

Docs: ensure "good commit message" examples actually follow guidelines (

  • Loading branch information...
not-an-aardvark committed Oct 16, 2017
1 parent ebb530d commit 47e5f6f8abef28286154421d3739b1532f029493
Showing with 1 addition and 1 deletion.
  1. +1 −1 docs/developer-guide/contributing/pull-requests.md
@@ -77,7 +77,7 @@ Here are some good commit message summary examples:
```
Build: Update Travis to only test Node 0.10 (refs #734)
Fix: Semi rule incorrectly flagging extra semicolon (fixes #840)
Upgrade: Esprima to 1.2, switch to using Esprima comment attachment (fixes #730)
Upgrade: Esprima to 1.2, switch to using comment attachment (fixes #730)
```
The commit message format is important because these messages are used to create a changelog for each release. The tag and issue number help to create more consistent and useful changelogs.

0 comments on commit 47e5f6f

Please sign in to comment.