ssh-key didn't checkout with ssh url

[lunawen]

Hi,
I've got a simple automated workflow for my static blog, here's my config:

- name: Checkout Repo
        uses: actions/checkout@v2
        with:
          ssh-key: ${{ secrets.DEPLOY_KEY }}

• I've got DEPLOY_KEY in my repo's secret,
• the public key is added to my user settings.
• The workflow can run successful

except when I use git remote get-url origin, I find it is still an HTTPS url.
I would like to have ssh url, is there anything I missed in this config?

Thanks for your help.

Luna

[ericsciple]

Is it a fork PR? Secrets aren't available during fork PRs.

[lunawen]

Hi Eric, thanks for your reply. It's not a fork PR, it's my private repo.

But today when I check again, it shows the remote url is ssh (hurray!)

The problem now is that, when I manually pull the repo in the remote server, it gives me error.

Any idea why is this happening?

[ericsciple]

I haven't seen that error before. Are you using a job container?

[lunawen]

Hi Eric,

Nope, here's my full workflow file, it is a basic one.

name: Deploy Site on push

on:
  push:
    branches:
      - master 

jobs:
  deploy: 
    runs-on: ubuntu-latest 

    steps: 
      - name: Checkout Repo 
        uses: actions/checkout@v2 
        with:
          ssh-key: ${{ secrets.DEPLOY_KEY }}

      - name: Deploy to Server 
        uses: AEnterprise/rsync-deploy@v1.0 
        env:
          DEPLOY_KEY: ${{ secrets.DEPLOY_KEY }} 
          ARGS: -avz --delete 
          SERVER_PORT: "22" 
          FOLDER: ./ 
          SERVER_IP: ${{ secrets.SSH_HOST }} 
          USERNAME: ${{ secrets.SSH_USERNAME }} 
          SERVER_DESTINATION: /var/www/xxx/ 

So this ssh error is not expected, right? As the workflow can use it without issue, it only happens when I log in the server and do it manually. Maybe something to do with my user role?

[ericsciple]

oh i see now.

No RSA host is known for github.com and you have requested strict checking

It looks like you might need to add github.com to your known_hosts file (for example) or turn of strict host checking

[awhitford]

Based on this:

    # Known hosts in addition to the user and global host key database. The public SSH
    # keys for a host may be obtained using the utility `ssh-keyscan`. For example,
    # `ssh-keyscan github.com`. The public key for github.com is always implicitly
    # added.
    ssh-known-hosts: ''

I would think that adding github.com as a known host should not be necessary.

[BondLi1]

when I ./config.cmd --name $runner_name --unattended --replace --runasservice in windows server,then I will get above error when run checkout action when use ssh way to clone code