Support for deploy keys

[paigeadelethompson]

When creating the deploy key for a repository like [email protected]:owner/repo.git or https://github.com/owner/repo, put that URL into the key comment. (Hint: Try ssh-keygen ... -C "[email protected]:owner/repo.git".)

doesn't work, did it really ever though?

[paigeadelethompson]

The reason why I ask is:

Added deploy-key mapping: Use identity '/home/runner/.ssh/key-9afee5aba32d34d4808381171428163bfab52f783f2c99f98ecce81fb90c9682' for GitHub repository xxxxxxxx

Run cargo build --verbose
warning: unused manifest key: source
    Updating crates.io index
    Updating git repository `xxxxxxxxxxxx`
warning: spurious network error (3 tries remaining): failed to resolve address for key-9afee5aba32d34d4808381171428163bfab52f783f2c99f98ecce81fb90c9682.github.com: Name or service not known; class=Net (12)

seems unlikely that ever worked :)

[wannieman98]

I spent quite some time, debugging through a different rabbit hole since the documentation seems to show that this was the answer. But I had ran into the same issue where, at the end, only the first ssh-private-key was picked up. Should the documentation be updated at this point to prevent confusion or has there been a fix already?