Any objections to this @nodegit/owners?

Hrm, I like that a lot for incrementals, not sure on the big update like this one. many of those PRs are fixing things introduced in the release, so it seems odd to include them in the changelog. At minimum, that is an awesome starting point, and potentially an all around solution in many cases (dot releases etc). Awesome awesome tool.

The only other thought is that currently we have history.md, this should be prepended there, either instead of included here, or in addition to (I'm not opposed to having a changelog for the latest version separate from the history).

@maxkorp thanks for mention it.
It will be a nice feature: to not include PR's, that fix closes another issues. I will research, how to implement it.

About excluding issues: this script can exclude/include issues by specific labels.

Interesting! That would be great, since we could exclude issues fixed that were introduced in the same release

@maxkorp so, what your opinion: is it better to exclude PR's or issues, that closed by PR from change log?

@skywinder can you also add a useful hash name to the header anchors? Something like

<a name="v0-0-6" href="some_gh_changelog">v0.0.6</a>

@tbranyen What do you mean? What should be in place of "some_gh_changelog"?
Now every tag name - is a link to this tag in project:
For example tag 0.2.4 links to https://github.com/nodegit/nodegit/tree/v0.2.4

We've brought this into our site, should we maintain a file in this repo as well?

@tbranyen
If you want to refer to specific tag in changelog (e.g. Add Anchor Tags To Jump To Specific Location On A Changelog), you can click on the chain image close with tag name:

And the browser will redirect you to the link with this tag as anchor:
( https://github.com/skywinder/nodegit/blob/add-change-log-file/CHANGELOG.md#v026-2015-01-20 in that case)
Is it a option, that you are looking for?

I think it's sort of customary to include the changelog with the source, yeah. We already have HISTORY.md but we can rename it and append it to this.

But now your history has only one tag.
I decide to take this name, because it's kind of standart. ( keepachangelog.com )

But you can specify your custom name for output file:

github_changelog_generator -o HISTORY.md

Yeah, I was saying keep this, and append the contents of history to this ;)

👍

@nodegit/owners how do you guys feel about merging this?

Yeah might as well. We can always change it later. Something is better than nothing.

Hooray, guys! 👍
BDW, I will add one feature soon: github-changelog-generator/github-changelog-generator#54
Since you are use quite different labels, rather than default github labels (Bug - bug, Modification- enhancement, Question - question) - this feature will help to make change log even more organised! I'll let you know when I'm done with it!