-
Notifications
You must be signed in to change notification settings - Fork 51
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
fix: Fix logic of useSSHAgent and needSSHKey #178
Conversation
* Fix logic of useSSHAgent and needSSHKey
Your change would cause g10k to try to load a ssh key even if there's no ssh key set in the g10k config. Do you use a private github.com repository with a ssh key by any chance? Otherwise g10k should skip any Can you trigger the original g10k I release with the |
needSSHKey = false | ||
} else { |
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.
I admit the the variable name needSSHKey
can be misleading. I renamed it to explicitlyLoadSSHKey
in the next version. Hopefully this helps understanding the logic.
We use an inhouse repository and the key is already loaded.
This is from your latest master without my patch and an inhouse repo, key already loaded and use_ssh_agent set to true true:
When i understand your comments and the documentation right, the ssh-add here is wrong. |
ah, needed to format your comment, which answers my question |
I guess I found it, do you use the |
Please try out https://github.com/xorpaul/g10k/releases/tag/v0.8.15 I've fixed the dedicated cache directories even in Because I'm using that to detect if the git repository that is being updated is a control repository, where a SSH key will be used if it is set in the g10k config and that did cause the wrong behavior of using the I've renamed the variable and fixed logic for using an SSH key working with git repositories here: |
Thank you very much. That fixed it. |
For us the fix in #171 did not work. g10k still asks for passwords with two different types of diaglogs. We fiddled around with the useSSHAgent and needSSHKey and this change works for us but i am not a go programmer and i don't know if it still works for the opposite usecase. Can you please take a lookg @xorpaul ?