zestia / hubrelease Goto Github PK

Include "revert" commits in release notes so you can tell if any pull request is reverted without having to open a new pull request for the revert.

The since param for the issues fetch is against the updated_at field, so updated issues (for example adding labels etc) would be included in a follow releases notes.

I think it'd be cool if you could use this to tag pre-release releases.

Imagine it'd work much the same as the current method in the sense that you give it a previously release tag and a new release tag, you would just give it a another flag to mark it as pre-release.

Scenario as follows:

1. PR 1 merged
2. build process started
3. PR 2 merged
4. build process completes and release notes generated

The release notes generated list PR 1 and PR 2 even though PR 2 is not actually included in the build.
The release on GitHub shows as "n commits to master since this release" where those commits are the commits from PR 2.

We encountered an issue where if you merge a pull request while a CI build was happening it would include it in the builds release notes, even though it was merged AFTER building.

Need to grab issues just before a tag was made to include those in the NEXT build properly.

Check the issue filtering is working for each filter. Noticed some PR/Issues missing when generating release notes for mobile beta releases.

Similar to how Github links/displays issues in their interface.

Specifiy a comma separated list of labels to include in the release notes text when that item has the label.