github-release-notes
github-release-notes copied to clipboard
Node module to create a release or a changelog from a tag and uses issues or commits to creating the release notes.
Adding the ability to release build artefacts would be very useful!
Thanks for such a useful tool. Current high level logic of `gren.js release --data-source=commits` is: - determine a date range - pick commits in master branch within this range -...
when running: `gren changelog --generate --tags 5.0.0..4.2.0 --override --data-source prs --debug` we're getting: ``` Options: Tags: 5.0.0,4.2.0 Prefix: v Template: [object Object] Prerelease: false Generate: true Quiet: false Override: true...
Not able to include issues closed under current tag in release notes. They get copied into next release notes.
We have a file `.grenrc.js` generated from `gren int` After adding a template object it looks like this: ``` module.exports = { "dataSource": "milestones", "prefix": "n", "groupBy": "label", "milestoneMatch": "{{tag_name}}",...
I created release from master branch tagged it and ran gren release. it added commits/prs from develop brnach too. Which were not even in master yet
I am trying to draft a new release using ``` gren release --tags=v3.0.6..3.0.7 ``` The following tag is not found in the repository: 3.0.7. please provide existing tags.
I have a private repo in Github which uses django for backend and react for frontend I like to have my changelog exposed to my endusers as well. If I...
When I run `gren changelog -B` on a public repo, I do get the following: ``` Options: Tags: empty Prefix: empty Template: [object Object] Prerelease: false Generate: false Quiet: false...