-
Notifications
You must be signed in to change notification settings - Fork 2
Add a body-text input, for describing the GitHub release #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to double check: did you verify this works? I.e. inserts the correct name.
That said, I wonder if we should not simply default to an empty string. Looking at https://github.com/gap-packages/aclib/releases/tag/v1.3.3 the "Release for AClib" in there doesn't really add any useful information. I know it's taken from classic ReleaseTools...
Anyway I modified an older release to have an empty body, turns out GitHub will then show some filler information that's not great either -- looks to me like the tag name and the commit message of the commit to which the tag is pointing?
Entering just a space as body doesn't help, it seems leading and trailing spaces are removed. I can use a non-breaking space entity
to get this look.So maybe "Release of BLA" is fine after all ...
Thanks for listening in to my random brain musings, tune in again tomorrow when we ask more weird off-topic questions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I agree with your sentiment here, the "Release for/of Package" doesn't really add anything. But if having the body be blank is not really possible, then I'm happy to keep the default as "Release for/of Package" instead.
It can always be changed in a future pull request anyway, I'm certainly not attached to it!