Skip to content
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

A note about the use of GPG signed commits #93

Closed
willdurand opened this issue Feb 11, 2017 · 2 comments
Closed

A note about the use of GPG signed commits #93

willdurand opened this issue Feb 11, 2017 · 2 comments

Comments

@willdurand
Copy link
Contributor

willdurand commented Feb 11, 2017

Edit: while filling this issue about a potential bug, I tried to investigate to give more hints about the bug I wanted to report. I discovered that VSCode had pretty much the same bug report, cf. microsoft/vscode#5065. I think it would be nice to add an entry to the FAQ maybe. I created this issue for documentation purpose anyway. Let me know if I can help on something.

TL;DR

If you get an error about tty and you do sign your commits, tell GPG not to use tty:

$ echo 'no-tty' >> ~/.gnupg/gpg.conf

Below is my original bug report:


Hi there!

Thanks for your great plugin, I cannot really use it (yet) but it looks very interesting so far!

How did it happen?

  1. Created a git repo (init) within Sketch (using the plugin)
  2. Added the current sketch file using the plugin
  3. Tried to commit with the plugin (did not check the input to generate pretty diffs)
  4. 💥

My git configuration is set to sign all my commits (cf. https://help.github.com/articles/telling-git-about-your-gpg-key/). Edit: For more information, see: microsoft/vscode#5065.

Error log

screen shot 2017-02-11 at 22 50 30

@mathieudutour
Copy link
Owner

Good to know thanks! Do you want to create PR with an entry in the FAQ?

@willdurand
Copy link
Contributor Author

Sure, I can do that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants