Release drafter should ignore prerelease releases when drafting changelog
See original GitHub issueSomewhat related to #614
I ran into an issue where someone had manually released a draft as prerelease, but the subsequently generated draft did not include the commits from the last stable release.
Presumably this is not intentional, but before I start working on this I’d like to make sure.
Thanks!
Issue Analytics
- State:
 - Created a year ago
 - Reactions:6
 - Comments:11 (8 by maintainers)
 
Top Results From Across the Web
release-drafter-github-app - npm
A GitHub app that draft releases based on pull-request labels. Latest version: 5.21.1, last published: 2 months ago.
Read more >release-drafter - Bountysource
Drafts your next release notes as pull requests are merged into master. ... Release drafter should ignore prerelease releases when drafting changelog $...
Read more >Stop writing your changelogs manually - Tiago Sousa
First of all, you need to run the action in a workflow so let's start by creating a new one! .github/workflows/release-drafter.yaml. name: ...
Read more >Releases - GitLab Docs
Other metadata associated with a released version of your code. Release notes. When you create a release: GitLab automatically archives source code and ......
Read more >Maintainers Guide — GMT 6.5.0 documentation
The Release Drafter GitHub Action will automatically keep a draft changelog at https://github.com/GenericMappingTools/gmt/releases, adding a new entry every ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

PR are always welcome 🤗
Obviously I’m not @jetersen, but having some experience with this project (and that this issue has not been rejected), I believe this patch would be accepted with some degree of enthusiasm (at least from me!).
The only alteration I would request is to make this setting configurable, but other than that I believe this is a very reasonable way to proceed. Thanks in advance!