{"action":"created","issue":{"url":"https://api.github.com/repos/sindresorhus/np/issues/61","repository_url":"https://api.github.com/repos/sindresorhus/np","labels_url":"https://api.github.com/repos/sindresorhus/np/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/sindresorhus/np/issues/61/comments","events_url":"https://api.github.com/repos/sindresorhus/np/issues/61/events","html_url":"https://github.com/sindresorhus/np/issues/61","id":164726817,"number":61,"title":"optional CHANGELOG generation with conventional-changelog-angular format","user":{"login":"bcoe","id":194609,"avatar_url":"https://avatars.githubusercontent.com/u/194609?v=3","gravatar_id":"","url":"https://api.github.com/users/bcoe","html_url":"https://github.com/bcoe","followers_url":"https://api.github.com/users/bcoe/followers","following_url":"https://api.github.com/users/bcoe/following{/other_user}","gists_url":"https://api.github.com/users/bcoe/gists{/gist_id}","starred_url":"https://api.github.com/users/bcoe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bcoe/subscriptions","organizations_url":"https://api.github.com/users/bcoe/orgs","repos_url":"https://api.github.com/users/bcoe/repos","events_url":"https://api.github.com/users/bcoe/events{/privacy}","received_events_url":"https://api.github.com/users/bcoe/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-07-10T18:04:59Z","updated_at":"2016-08-02T16:46:16Z","closed_at":null,"body":"## Problem Statement\r\n\r\nI've become a convert to using a [conventional commit format](https://github.com/bcoe/conventional-changelog-standard/blob/master/convention.md) when squashing commits on my various OSS projects:\r\n\r\n* with `nyc` and `yargs` I was finding it valuable to (and people requested that I) maintain a CHANGELOG:\r\n  * it's useful for forensic analysis when bugs are released.\r\n  * it helps communicate outwards to the community about the work you're doing.\r\n* unfortunately, I found that CHANGELOG maintenance was a nuisance -- it would add several minutes (at best) to the release cycle while I groomed the file, and collected information for it.\r\n\r\nI wanted a CHANGELOG, but I didn't want to put work into maintaining it!\r\n\r\n## The Solution\r\n\r\n* I *don't* require that contributors to the project use a special commit format.\r\n* I take advantage of GitHub's [squash button](https://help.github.com/articles/about-pull-request-merge-squashing/), and craft a formatted message while I land pull requests (this adds almost no cycles to my workflow).\r\n* I currently use the [standard-version](https://github.com/conventional-changelog/standard-version) tool to cut a release from the git history that has been landed.\r\n\r\nHere's what you end up with:\r\n\r\nhttps://github.com/yargs/yargs/blob/master/CHANGELOG.md\r\n\r\n## Proposal\r\n\r\n* it would be great if we could add CHANGELOG support to `np`.\r\n* rather than requiring this functionality (I understand not everyone will want to craft commit messages) we could add a new option flag `--changelog`?\r\n\r\n## Why?\r\n\r\nVarious folks in the [conventional-changelog org](https://github.com/conventional-changelog) have expressed an interest in working together more closely with you (CC: @nexdrew, @Tapppi).\r\n\r\nPersonally, I'd like to find ways to continue standardizing on commit message format/release management. I'm excited by projects like @boennemann's [semantic-release](https://github.com/semantic-release/semantic-release), I've also been talking to the folks at coveralls.io about the idea of creating activity feeds for your coverage history based on parsing this format (CC: @nickmerwin, @anjin).\r\n\r\ntldr; there's lots of cool stuff happening around CI/CD right now, and we should try to work together as much as possible.\r\n"},"comment":{"url":"https://api.github.com/repos/sindresorhus/np/issues/comments/236965833","html_url":"https://github.com/sindresorhus/np/issues/61#issuecomment-236965833","issue_url":"https://api.github.com/repos/sindresorhus/np/issues/61","id":236965833,"user":{"login":"dignifiedquire","id":790842,"avatar_url":"https://avatars.githubusercontent.com/u/790842?v=3","gravatar_id":"","url":"https://api.github.com/users/dignifiedquire","html_url":"https://github.com/dignifiedquire","followers_url":"https://api.github.com/users/dignifiedquire/followers","following_url":"https://api.github.com/users/dignifiedquire/following{/other_user}","gists_url":"https://api.github.com/users/dignifiedquire/gists{/gist_id}","starred_url":"https://api.github.com/users/dignifiedquire/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dignifiedquire/subscriptions","organizations_url":"https://api.github.com/users/dignifiedquire/orgs","repos_url":"https://api.github.com/users/dignifiedquire/repos","events_url":"https://api.github.com/users/dignifiedquire/events{/privacy}","received_events_url":"https://api.github.com/users/dignifiedquire/received_events","type":"User","site_admin":false},"created_at":"2016-08-02T16:46:15Z","updated_at":"2016-08-02T16:46:15Z","body":"I'm actually in need of exactly this and currently trying to figure out if there is a nice way where I don't have to fork`np`, so I would be very interested in working on this and figuring out a nice solution so I don't have to duplicate all the work that already is in `np`."}}
{"actor":{"display_login":"dignifiedquire"}}