# PR Changelog A script to generate a nice list of changes given two git references. It takes in account all the merged pull request to master between the two given references, then it formats it in a nice consumable way. To be effective, this script requires that you follow simple conventions: 1. Your pull request titles must be written as changelog entries 2. (Optional) Your project has git tags for each version you release (example: `0.3.0`) 3. (Optional) Your pull request titles begin with some sort of tag (`Feature`, `Improvement`, `Fix`, `Internal`) Then a sample pull request title would be: > Feature: shake the phone to send feedback email ## Installation Add this line to your application's Gemfile: ```ruby gem 'pr_changelog' ``` And then execute: ```shell $ bundle ``` Or install it yourself as: ```shell $ gem install pr_changelog ``` ## Usage To get the changes between to git tags `0.3.0` and `0.5.0`, execute: ``` $ pr_changelog 0.3.0 0.5.0 ``` Will produce: ```markdown ## Changes since 0.3.0 to 0.5.0 [New features] - #61: ⭐️ Shake the phone to send feedback email [Improvements] - #64: πŸ’Ž Visual refinements for canvas 2.0 - #57: πŸ’Ž Memory performance tweaks - #62: πŸ’Ž Visual polishing for top stories [Internal] - #65: πŸ‘¨β€πŸ’» Add formatting rules for xml files - #60: πŸ‘¨β€πŸ’» Setup hockeyapp for crash reporting ``` or ``` $ pr_changelog --format plain 0.3.0 0.5.0 ``` Will produce something like: ```markdown ## Changes from 0.3.0 to 0.5.0 - #64: Improvement: visual refinements for canvas 2.0 - #65: Internal: add formatting rules for xml files - #63: Feature: Add Footer story - #57: Improvement: Memory performance tweaks - #61: Feature: shake the phone to send feedback email - #62: Improvement: visual polishing for top stories - #60: Internal: setup hockeyapp for crash reporting ``` ## Contributing Bug reports and pull requests are welcome on GitHub at https://github.com/schibsted/pr_changelog. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. ## License The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT). ## Code of Conduct Everyone interacting in the `pr_changelog` project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/schibsted/pr_changelog/blob/master/CODE_OF_CONDUCT.md).