Skip to content

Instantly share code, notes, and snippets.

@adonaldson
Created September 5, 2011 17:55
Show Gist options
  • Save adonaldson/1195558 to your computer and use it in GitHub Desktop.
Save adonaldson/1195558 to your computer and use it in GitHub Desktop.
Output from Git
Mon, 5 Sep 2011
Changes between 'ea776f90655ded3da3e1cf3b1f077b22b7ff0401' and HEAD
FEATURE:
- Hello world, now with added 3
BUGFIX:
- Forgot to add version 2
OTHER:
- Re-added hello_world.txt for backward compatibilty
commit ec510a59a2e35670c67abdfbbda64ef20d680ffd
Author: Andrew Donaldson <[email protected]>
Date: Mon Sep 5 18:54:19 2011 +0100
FEATURE: Hello world, now with added 3
commit e03388528e1fb5dfffd11e70772893b8f669ddd2
Author: Andrew Donaldson <[email protected]>
Date: Mon Sep 5 18:53:29 2011 +0100
Re-added hello_world.txt for backward compatibilty
commit 460bea131c1dff3064f5aa3eb07ac23a60db379b
Author: Andrew Donaldson <[email protected]>
Date: Mon Sep 5 18:53:01 2011 +0100
BUGFIX: Forgot to add version 2
commit ea776f90655ded3da3e1cf3b1f077b22b7ff0401
Author: Andrew Donaldson <[email protected]>
Date: Mon Sep 5 18:52:43 2011 +0100
FEATURE: Added hello_world.txt
@adonaldson
Copy link
Author

I wrote a script a while back that would take git commit messages and turn them into a basic changelog. I'd rather that the categorising word (FEATURE or BUGFIX) isn't shortened, but I'm also wary of adding too much noise to the commit messages.

Can anyone think of a better way to add this data to commits? Perhaps it could be the first line of the commit body (where in my head the top line being the title and the third line being the body), that way it'd keep the oneline commit message to the point.

Does this idea offend anyone? Just trying to figure out whether it's worth tidying the code a little to put online or whether it's just a nice little script for me and me only :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment