-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Improve gh release create --notes-from-tag behavior with multiline tag annotation
#9385
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
andyfeller
merged 7 commits into
cli:trunk
from
babakks:9299-improve-annotated-releases
Aug 12, 2024
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b996380
Use signature-stripped tag annotation content
babakks df3b062
Add test for `gitTagInfo`
babakks 46814b3
Add example for `--notes-from-tag`
babakks 8ea1b89
Update tests with changes to `gitTagInfo` function
babakks b36b39d
Explain why not looking for signature begin marker
babakks 668dbce
Add test cases for PGP, SSH and X.509 signatures
babakks 6dc7297
Merge branch 'trunk' into 9299-improve-annotated-releases
babakks 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
Oops, something went wrong.
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.
Updating this function to return empty string for the body if an error is raised makes sense. That said, I wonder if that was always the case. 🤔
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. Since it's the result of a command execution, it's possible to have non-nil value for both error and result. But obviously, when there's an error the result value is unreliable. Esepcially, when it's the stdout of a command, which, for example, can be an error message.
Interestingly, the caller of this function, ignores the error which makes it even more risky.
I think we should:
gitTagInfo, return"", errwhen there's an error (as it's already done in this PR).What do you think?