-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feat: support gpg sigin commit. #53
base: master
Are you sure you want to change the base?
Conversation
Great job! Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
Codecov Report
@@ Coverage Diff @@
## develop #53 +/- ##
===========================================
- Coverage 40.82% 38.24% -2.59%
===========================================
Files 11 11
Lines 556 604 +48
===========================================
+ Hits 227 231 +4
- Misses 329 373 +44
Continue to review full report at Codecov.
|
progress reportRecently, I realized that perfectly supporting Ref |
|
||
self.after_commit()?; | ||
/// check gpg is available, if true then using gpg sign commit. | ||
/// github.com/sdttttt/gcr/issues/52 Thinks @Enter-tainer @CoelacanthusHex |
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.
thinks -> thanks?
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.
Thank you for pointing out the mistake. I'll fix it before we finish.
We had the same feature request for git-cm: mainrs/git-cm#16. If you figure out an alternative, let me know :) |
@sirwindfield, as you said, the FFI compilation of `gpg-rs/ gpgme` does cause some trouble for non-unix platforms, so I'm recently looking for a more native GPG implementation in Rust. What has caught my attention are two GPG implementations that might be helpful, `gpgrv` and `sequoia- openpgp`, but they have one thing in common, that is, the API provided is more low-level and obscure. I don't know the details of OpenGPG encryption. It is very difficult for me to start with them.
…---
发件人: SirWindfield
发送时间: 2021年3月21日 20:09
收件人: sdttttt/gcr
抄送: Ryn; Assign
主题: Re: [sdttttt/gcr] Feat: support gpg sigin commit. (#53)
We had the same feature request for git-cm: mainrs/git-cm#16.
I hesitated as well as I couldn't get Windows support to work. Linking gpgme on Windows is unreliable as not everybody has Gpg4Win installed. Secondly, it would force the binary to run in 32bit mode. Not a dramatic consequence, but one that you should be aware off.
If you figure out an alternative, let me know :)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I'm in the same boat. I have not much internal knowledge of GPG to be confident enough to provide an implementation that I can be sure of works properly. That's why I didn't implement the feature for now. I've opened an issue for |
Feature
grc
will submit with an implicitGPG
signature. This feature does not require configuration. (Close commits generated by grc are not properly signed #52)