-
-
Notifications
You must be signed in to change notification settings - Fork 301
Sign tag #522
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
Sign tag #522
Conversation
(削除) pipeline error seems nothing related to my changes, please let me know how to retry the jobs or how to fix them. (削除ここまで)
Codecov Report
@@ Coverage Diff @@ ## master #522 +/- ## ========================================== + Coverage 97.92% 98.01% +0.09% ========================================== Files 39 39 Lines 1540 1565 +25 ========================================== + Hits 1508 1534 +26 + Misses 32 31 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Awesome work @gpongelli 💪🏻
This reverts commit 9d72ea9.
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.
@Lee-W looks good to me, if you are ok with it we merge
@woile what do you think about this comment ?
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.
What's the expected output of chardet.detect
if it cannot detect anything? Will it be something like {'encoding': None, 'confidence': 0.99}
?
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.
What's the expected output of
chardet.detect
if it cannot detect anything? Will it be something like{'encoding': None, 'confidence': 0.99}
?
Yes, it returns None, that's why I've added the or
clause.
It also returns None for empty content b''
, like the stderr content when all goes ok, so the or
is mandatory to avoid decode
failures.
Let me know if this "chardet-enabled" version is ok or if you prefer the previous one (with "iso..." encoding).
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 confirm it. I like the chatdet idea.
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.
Thanks for your contribution! let's merge it and release a new version 🎉🎉🎉
Description
Add tag sign feature for bump command.
Checklist
./scripts/format
and./scripts/test
locally to ensure this change passes linter check and testExpected behavior
When added the
--signed-tag
, bump command will sign the tag with preconfigured GPG private key.Steps to Test This Pull Request
cz bump --signed-tag <tag>
git tag -v <tag>
that the stdout answer starts withgpg: Signature made
stringA new method to check if the tag is signed was added to do same step of point 2 above.
Additional context