GPG commit error message

Please summarise the issue in the title, and then use the template below to fill out the details so we can reproduce the issue on our end.

Description

I use GPG key in my commits, and when i commit through the app it gives an error.

Version

What version of GitHub Desktop are you running? This is displayed under the About GitHub Desktop menu item. If you are running from source, include the commit by running git rev-parse HEAD from your local repository.

GitHub Desktop version: 0.6.0

The operating system you are running on may also help with reproducing the issue:

• If you are on macOS, launch About This Mac and write down the OS version listed.
• If you are on Windows, open Command Prompt and attach the output of this command*: cmd /c ver

OS version: 10.12.5

Steps to Reproduce

1. write a commit message
2. commit to master

If the issue involves a specific public repository, including the information about that repository will make it is easier to recreate the issue.

If you think screenshots or a GIF recording will help demonstrate the issue better, feel free to add them here.

Expected behaviour: commit message and ask for password

Actual behaviour: Commit failed - exit code 128 received, with output: 'error: gpg failed to sign the data fatal: failed to write commit object'

Reproduces how often: every time i have a repository with gpg enabled

Logs

There may be some relevant information in log files generated by GitHub Desktop:

• If you are on macOS, attach the most recent log file from: ~/Library/Application Support/GitHub Desktop/logs/*.desktop.production.log
• If you are on Windows, attach the most recent log file from: %APPDATA%\\GitHub Desktop\\logs\\*.desktop.production.log

The log files are organized by date, so see if anything was generated for today’s date.

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

If you are dealing with a performance issue or regression, attaching a Timeline profile of the task will help the developers understand the runtime behaviour of the application on your machine.

[shiftkey]

As this is dependent on the work in #78, I’ve added a comment about this flow to that issue and will close this out. Thanks for the report, please follow along with #78 for implementing this as a first-class feature!

[shiftkey]

As a workaround, I’d recommend looking at serving up the password using gpg-agent with a setup like this until we can get to this.