Consider commiting with --no-gpg-sign
#30
Comments
tkw1536
added a commit
to tkw1536/git-fire
that referenced
this issue
Aug 27, 2017
When using git 2.x and the `commit.gpgsign` option is enabled, each commit is automatically signed with gpg. As noted by @johnp this usally means that the user has to enter a password, or unlock the gpg using some other method. This is a problem when having to leave the building because of fire. This commit solves the problem by adding the --no-gpg-sign flag to the `git commit` invocation if the git version being used starts with a "2". This is achieved by checking the output of `git version` and using grep to match the version number.
tkw1536
added a commit
to tkw1536/git-fire
that referenced
this issue
Aug 27, 2017
When using git 2.x and the `commit.gpgsign` option is enabled, each commit is automatically signed with gpg. As noted by @johnp this usally means that the user has to enter a password, or unlock the gpg using some other method. This is a problem when having to leave the building because of fire. This commit solves the problem by adding the --no-gpg-sign flag to the `git commit` invocation if the git version being used starts with a "2". This is achieved by checking the output of `git version` and using grep to match the version number.
tkw1536
added a commit
to tkw1536/git-fire
that referenced
this issue
Aug 27, 2017
When using git 2.x and the `commit.gpgsign` option is enabled, each commit is automatically signed with gpg. As noted by @johnp this usally means that the user has to enter a password, or unlock the gpg key using some other method. This is a problem when having to leave the building because of fire. This commit solves the problem by adding the --no-gpg-sign flag to the `git commit` invocation if the git version being used starts with a "2". This is achieved by checking the output of `git version` and using grep to match the version number.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a user has GPG signature by default enabled in
.gitconfigthe GPG agent may require password input or a security key which should be skipped in case of fire.The text was updated successfully, but these errors were encountered: