bramdevries/changelog

A http://keepachangelog.com/ parser for the common developer

Changelog

Parse changelogs like a pro, _(*1)

This package makes it easy to parse change logs in the keepachangelog.com format, _(*2)

Installation

composer require bramdevries/changelog, _(*3)

Usage

Parsing an entire change log

The following change log:, _(*4)

```md, <sub>(*5)</sub>

# Change Log A change log for the change log parser, <sub>(*6)</sub>

## 0.2.0 - 2014-11-22, <sub>(*7)</sub>

### Added, <sub>(*8)</sub>

• getChanges method to retrieve a single release, <sub>(*9)</sub>

  0.1.0 - 2014-11-22

  Added

• getReleases method that retrieves the releases described in a change log, <sub>(*10)</sub>

• toJson method that creates a json representation of a change log., <sub>(*11)</sub>

  ```, <sub>(*12)</sub>

$parser = new Changelog\Parser(file_get_contents('CHANGELOG.md');
echo $parser->toJson();

Will return, <sub>(*13)</sub>

{
  "description": "A change log for the change log parser",
  "releases": [
    {
      "name": "0.0.1",
      "date": "2014-11-22",
      "changes": {
        "added": [
          "<code>getReleases</code> method that retrieves the releases described in a change log",
          "<code>toJson</code> method that creates a json representation of a change log."
        ]
      }
    }
  ]
}

Parsing a single release's changelog

eg: If you want to parse a pull request in this format, <sub>(*14)</sub>

  ### Added
  - Addition 1
  - Addition 2

  ### Changed
  - Change 1
  - Change 2

  ### Removed
  - Removal 1
  - Removal 2

// Assuming $content contains the above markdown
$parser = new Changelog\Parser($content);
echo $parser->getChanges();

returns, <sub>(*15)</sub>

{
  "added": [
    "Addition 1",
    "Addition 2"
  ],
  "changed": [
    "Change 1",
    "Change 2"
  ],
  "removed": [
    "Removal 1",
    "Removal 2"
  ]
}