[
https://issues.apache.org/jira/browse/YETUS-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015092#comment-16015092
]
Suraj Acharya commented on YETUS-315:
-------------------------------------
So it has been a few weeks since I wrote this and here are a few thoughts of my
own and would appreciate peoples ideas.
* Currently setting an environment variable {{GPGSIGN=true}} will make it
similar to the {{--gpg-sign}} flag.
* If someone doesnt have the keys setup then there is a gpg error.
However, now the other question is that if someone has gpg keys setup for
[email protected] and is now trying to commit using the id [email protected], it
will fail with unable to find key. Is this a valid case? or is this something
which is not common?
> smart-apply-patch committer mode should support signed commits
> --------------------------------------------------------------
>
> Key: YETUS-315
> URL: https://issues.apache.org/jira/browse/YETUS-315
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Suraj Acharya
> Fix For: 0.5.0
>
>
> A new {{--gpg-sign}} flag is added to the smart-apply-patch.sh.
> This will allow the committer to sign the commit.
> GPG Agent will handle the passphrase request.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
