suddenly broken?

[rkurchin]

Without any changes to my repo (or the SSH keys/settings) in the past month, CompatHelper has started erroring 7 days ago with a bunch of copies of:

Cloning into 'REPO'...
Warning: Permanently added the RSA host key for IP address '140.82.113.4' to the list of known hosts.
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

You should be able to see full output here (I hope...).

There's a lot missing from my understanding of how these workflows work, interact with permissions, etc., so I haven't had much luck troubleshooting....any advice appreciated!

[DilumAluthge]

@mattBrzezinski @fchorney Any idea what might be going on here?

[fchorney]

If nothing has changed with compathelper, and nothing has changed in your repo or ssh settings and I'm not really sure. For some reason github decided it didn't like the SSH key :/ Would it be possible to make a new key and try using that?

It looks like it's just straight up failing on a basic git clone of the project git clone [email protected]:rkurchin/Nodariety.jl.git REPO

[DilumAluthge]

Yeah I would say the first step is to regenerate the key.

@rkurchin You can use the DocumenterTools.jl package. E.g. DocumenterTools.genkeys(). It'll produce the private key, which needs to go into a secret in GitHub, where the secret is named DOCUMENTER_KEY. And the public key, which needs to be a deploy key. Make sure that the deploy key has write access.

[rkurchin]

Regenerating the keys seemed to fix it. Thanks! (Might be worth a remark in the docs somewhere?)