chg
unfancy release history tracking
functions:
init
- create a CHANGELOG.md fileadd
- add new changes to the changelog under a 'HEAD (Unreleased)' headingrelease
- move all unreleased changes under a new release version
chg
can be useful when built into a release/deploy script or paired with a pull request merging script like pulley.
It does not try to automatically generate changes from git commits or github pull requests, though you could build that on top of the chg
functions.
Example
CHANGELOG
=========
## HEAD (Unreleased)
* Removed crusty semantic html, javascript app ftw
--------------------
## 2.0.0 (2007-3-13)
* Removed horrible tables, semantic html ftw
* Switched background to vertical gradient
* Added dropshadows to EVERYTHING
## 1.1.1 (2002-08-16)
* Added "dot.gifs" to ~300 table cells to fix layout issues
## 1.1.0 (2002-05-17)
* Removed horrible Flash, table layout ftw
* Switched background to horizontal gray lines
## 1.0.1 (2000-07-01)
* Duplicated all Flash content in HTML so Yahoo can see it
## 1.0.0 (2000-04-14)
* Removed horrible frames, Flash ftw
* Switched background to fast moving clouds like 2advanced V3
## 0.1.0 (1997-01-26)
* Added a "GIF" of a construction worker. ha ha ha
* Navigation frame ftw
* Added repeating tanbark background to look more professional
Using globally
[sudo] npm install -g chg
chg init
chg add 'My first change'
chg release '0.0.1'
Using as a node module
shell
# install
npm install chg --save
javascript
var chg = require('chg');
chg.init({}, callback);
chg.add('My first change', {}, callback);
chg.release('0.0.1', {}, callback);
Using as a grunt plugin
shell
# install
npm install chg --save-dev
Gruntfile.js
grunt.loadNpmTasks('chg');
shell
# create CHANGELOG.md
grunt chg-init
# add a change
grunt chg-add
# create a release
grunt chg-release
Release History
See CHANGELOG.md :scream-cat:
License
Copyright (c) 2014 heff. Licensed under the Apache license.