Skip to content

Commit

Permalink
Advise wrapping commit messages to 72 characters
Browse files Browse the repository at this point in the history
This seems to be standard good practice.
  • Loading branch information
ojwb committed May 27, 2017
1 parent 11bfd18 commit 3d8831a
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion contributing/workflow.rst
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,8 @@ you!
bug on OS X"). This matches git's automatic messages around
merges, reverts and so on.

* Follow that with more detail as needed.
* Follow that with more detail as needed, wrapping long lines at
72 characters (one exception is that long URLs are best not wrapped).

* Describe the effect, not the code. The important thing is for
people to be able to read the commit message and understand what
Expand Down

0 comments on commit 3d8831a

Please sign in to comment.