feat: Implementing the Release Notes Generator to the project.#112
Merged
Conversation
tmikula-dev
requested review from
MatloaItumeleng,
Zejnilovic,
benedeki,
dk1844,
lsulak and
yruslan
as code owners
|
JaCoCo code coverage report - scala 2.12.20
No changed file in reports. Run 28573824041 · Event: |
MatloaItumeleng
approved these changes
Jul 2, 2026
MatloaItumeleng
left a comment
MatloaItumeleng
left a comment
Contributor
There was a problem hiding this comment.
LGTM , thank you
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This pull request introduces improvements to the release workflow by adding a new PR template and two GitHub Actions workflows for managing and verifying release notes. These changes help standardize release note practices and automate checks and draft releases.
Release Notes
no RNlabel to the projectRelated
Closes #98