-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too many draft releases from release drafter #18319
Comments
I can do the monkey work this evening, have some time. |
@atomfrede : only keep the most recent one :-) |
I will now remove all drafts except the last one and try to exclude certain PRs from release drafter (especially dependabot, it's really too much) |
I have also removed the latest draft, such that release drafter can create a new one with correct date too. |
At first it looks good imho. Drafted release notes are empty by default, added the release-notes label to certain PRs. |
Works fine, let's close this, if we need to/want to further adapt the config let's do that in another issue. |
Bounty claimed https://opencollective.com/generator-jhipster/expenses/71751 |
@atomfrede the release-notes tag is required? The 2 first v7.8.1 release note entries are not included at the release. |
My idea was to mark entries explicit to make them eligible for the release note page |
IMO we should add every PR to release note, just keep Dependabot out. |
I'm fine with what @mshima suggests |
Also fine for me, guess keeping them out will help already to have better release notes. |
except dependabot PRs updates jhipster#18319
Updated the config with #18327 |
It seems like there are too many draft releases created by release drafter as if it's being created for every merge. We should change it so that its generated only when a new tag is pushed
Also the dates on the created draft seems to be wrong
https://github.com/jhipster/generator-jhipster/releases.
The text was updated successfully, but these errors were encountered: