You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running do ##class(SourceControl.Git.API).Configure(), the user is prompted to provide an SSH key with this message:
Path to private key file for SSH remotes; if file does not exist, later prompts will help set it up with proper ownership:
If I leave this blank and proceed to clone a repository, I am never prompted to create an SSH key through the script even though this text tells me I should expect that.
Is the SSK Key prompt referring to the GUI (where it sometimes provides a button to facilitate creating a key) or later in the Configure script? Best case is that this instruction just needs clarification. Worst case, this is a feature that is not working as intended.
(for what it's worth, when I first create an SSH key myself and configure the public part in github/bitbucket, the clone process works.)
The text was updated successfully, but these errors were encountered:
The prompt could definitely use some clarification. The expected behavior here is that:
if I do not enter a file path, no SSH key is created
if I do enter a file path and the file exists, no SSH key is created
if I do enter a file path and the file does not exist, another prompt will show up at the end asking if an SSH key should be created.
How about this as the prompt? "Path to private key file for SSH remotes; if a path is provided and file does not exist, later prompts will help set it up with proper ownership:"
That's on the right track, but I think we can do better. How about this?
Path to an SSH private key file for remote interactions. (If a path is provided and the file does not exist, then this script will walk you through creating one. Leave blank to skip.)
When running
do ##class(SourceControl.Git.API).Configure()
, the user is prompted to provide an SSH key with this message:If I leave this blank and proceed to clone a repository, I am never prompted to create an SSH key through the script even though this text tells me I should expect that.
Is the SSK Key prompt referring to the GUI (where it sometimes provides a button to facilitate creating a key) or later in the Configure script? Best case is that this instruction just needs clarification. Worst case, this is a feature that is not working as intended.
(for what it's worth, when I first create an SSH key myself and configure the public part in github/bitbucket, the clone process works.)
The text was updated successfully, but these errors were encountered: