Add semi-automated tagging and generating GH Release draft to CICD #37
Conversation
This file contains 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
JaCoCo code coverage report - springdoc-openapi-scala-1
|
JaCoCo code coverage report - springdoc-openapi-scala-2
|
…ating-gh-release-draft-to-release-workflow
dk1844
previously approved these changes
Jan 12, 2024
jakipatryk
added
the
work in progress
jakipatryk
changed the title
jakipatryk
removed
the
work in progress
miroslavpojer
approved these changes
Jan 12, 2024
jakipatryk
deleted the
feature/add-semi-automatic-tagging-and-generating-gh-release-draft-to-release-workflow
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
openjdk@1.17.01inpublishjob, as this was already needed in CIrelease_draftwith:tagjob that creates and pushes a git tag (name is specified as the workflow input)releasejob that creates a draft release with notes derived from closed issuesrelease_publishwithpublishjob that was previously in thereleaseworkflow; now it should be triggered once release created byrelease_draftis finalised and converted from draft to release