Looks great. To avoid all PR in the first release we can add an empty release note for the latest release tag and then the new release draft should contains only PR from the latest release not all.
śr., 9 lut 2022 o 05:10 Olivier Lamy <ol...@apache.org> napisał(a): > Hi > Github has a feature to attach a release note to tag/release. > The content is then used when dependabot generates his famous PR all > over the world!! (yup a maven plugin generates a lot!!) > Our current content is not very user friendly.... > > While preparing the maven-compiler-plugin new release I have made some > tests using release-drafter tool [1]. > This generates the content here: > https://github.com/apache/maven-compiler-plugin/releases > The release notes will automatically contains only content from PRs (PR > must have a label to appear in a dedicated section otherwise they will be > in the top, see mapping label/section here [2]) > This mapping is a default which can be shared between all project so the > configuration is very simple see [3]. > Please note the first time it's used the first release will > contain everything (all PRs) from the start as there is no first release. > The process is manual at the end, after all of our release process steps, > you just need to go to GH ui then publish the release (manual. > modifications still possible). > > comments? thoughts? complaints :)? > > cheers > Olivier > > PS: if you want to use this be sure to modify manually the content before > the publish as the content is regenerated for every merge PR > > [1] https://github.com/release-drafter/release-drafter > [2] > > https://github.com/apache/maven-gh-actions-shared/blob/main/.github/release-drafter.yml > [3] > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/release-drafter.yml > and > > https://github.com/apache/maven-compiler-plugin/blob/master/.github/workflows/release-drafter.yml > -- Sławomir Jaranowski
