summaryrefslogtreecommitdiff
path: root/HACKING.rst
diff options
context:
space:
mode:
authorSteven Dake <sdake@redhat.com>2013-02-28 14:42:00 -0700
committerSteven Dake <sdake@redhat.com>2013-03-04 11:20:31 -0700
commit137f9c0ad2b7c8d542c051ece2527b4c9d182817 (patch)
treecc4b1190859ee0f8aa7d53817ad05d6cc302243b /HACKING.rst
parentc4248dd0d763ef87ff55fb1847530253d33e85ba (diff)
downloadheat-137f9c0ad2b7c8d542c051ece2527b4c9d182817.tar.gz
Add N802 rule to hacking.py
Gate on commit headers < 50 characters Change-Id: Ia6a616d8a9b0eabca05a23476e284f261108b43a Fixes: Bug #1136386
Diffstat (limited to 'HACKING.rst')
-rw-r--r--HACKING.rst3
1 files changed, 1 insertions, 2 deletions
diff --git a/HACKING.rst b/HACKING.rst
index 2692e7af5..41dc8cbba 100644
--- a/HACKING.rst
+++ b/HACKING.rst
@@ -271,8 +271,7 @@ Commit Messages
Using a common format for commit messages will help keep our git history
readable. Follow these guidelines:
- First, provide a brief summary (it is recommended to keep the commit title
- under 50 chars).
+ First, provide a brief summary 72 characters in length or less.
The first line of the commit message should provide an accurate
description of the change, not just a reference to a bug or