JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 1050
  • Score
    100M100P100Q102238F
  • License MIT

Make a changelog from git commits, tags, and releases

Package Exports

  • better_git_changelog
  • better_git_changelog/src/js/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (better_git_changelog) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

better_git_changelog

Make a changelog from git commits, tags, and releases

npm install --save better_git_changelog
better_git_changelog

 

 

What's this, then?

Other changelog making tools were too complex and didn't do what I want. One was close, but didn't cleanly handle the mix of 1.0.0 and v1.0.0 in the history, and didn't give links to relevant branches.

So, I made a zero-config CHANGELOG tool.

This is generally intended to be used as a step in the ends of build chains. The author uses it by making a command changelog in the scripts block of any project's package.json, then writing better_git_changelog in there, and can now issue npm run changelog to receive bacon.

 

 

What does it look like?

There's an example here.