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
Besides making sure that the key is correct (that it's the private and not the public, it's complete...), I guess a good test to help identify the problem could be replace the content of the key by some random text, and echo it and see that we're ready getting the full content with no garbage in it.
I think just few people have access to it, @TomAugspurger do you have time for it? Or do you know who else has access to the settings? I think it was said in some thread, but I fail to remember.
The text was updated successfully, but these errors were encountered:
Thanks @TomAugspurger. Looks like we still got the same error, so I guess the problem is something else. I'll do some tests in a separate repo, and see if I can reproduce the problem.
Looks like using the ssh key to publish the development web and docs is not working. The error we get in the CI is that the key has an invalid format.
I guess it's not as simple as the key content being incorrect, I guess it can't be obtained from the secrets, and probably the used key is just empty.
The relevant code is in the yaml of the GitHub action.
Besides making sure that the key is correct (that it's the private and not the public, it's complete...), I guess a good test to help identify the problem could be replace the content of the key by some random text, and echo it and see that we're ready getting the full content with no garbage in it.
I think just few people have access to it, @TomAugspurger do you have time for it? Or do you know who else has access to the settings? I think it was said in some thread, but I fail to remember.
The text was updated successfully, but these errors were encountered: