On Thu, 10 Feb 2022 at 02:04, Tamás Cservenák wrote:
> Howdy,
>
> Yes, looks good, but one thing bothers me:
> Does this mean that Maven projects -- if release-drafter is to be used --
> will have their release notes stored and accessible in their mirror
> repositories only?
>
I do not see
Hello everyone,
For what’s worth JReleaser supports a similar set of features for creating a
changelog based on Git history.
For the time being JReleaser categorizes commit messages following your own
conventions. The rules are inspired by release-drafter.
The pros are:
- set up your own
Howdy,
Yes, looks good, but one thing bothers me:
Does this mean that Maven projects -- if release-drafter is to be used --
will have their release notes stored and accessible in their mirror
repositories only?
T
On Wed, Feb 9, 2022 at 4:57 PM Slawomir Jaranowski
wrote:
> Looks great.
>
> To
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 napisał(a):
> Hi
> Github has a feature to attach a release
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
