Allow optional configuration of the GitHub release announcement body #23
Conversation
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
Member
Author
Member
Author
|
I don't know of a way to test this change. I did write some local shell scripts trying out the logic and they worked for the most part. The only oddity was handling of newlines, but as far as I could tell the original here-doc text had the same issue so 🤷♂️ |
Member
Author
|
No, that file is hand-written, and specific to branch. |
beikov
approved these changes
Nov 19, 2024
Member
Author
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Hibernate ORM keeps a file
/release_announcement.adocin its source tree. This change allows us to include that text into the body of the release announcement created for the GitHub release via an optional argument.