Cannot use SSH key

[Gameking1happy]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Actions Checkout

Discussion Details

  Load key "/home/runner/work/_temp/1facdcd8-74b4-4c09-9880-f9039d8151ef": error in libcrypto
  git@github.com: Permission denied (publickey).
  Error: fatal: Could not read from remote repository.

I get the error above, below is the yml.

on:
  workflow_dispatch:
jobs:
  test:
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
      - name: Checkout
        uses: actions/checkout@v4
        with:
          ssh-key: ${{ secrets.DEPLOY_KEY }}
      - name: Identify
        run: |
          git config --global user.email "github-actions@github.com"
          git config --global user.name "github-actions"
      - name: test
        run: |
          touch test.txt
          git add test.txt
          git commit -m "test"
          git push origin HEAD:main

[phgoncalves2603]

That error

Load key "/home/runner/work/_temp/...": error in libcrypto
git@github.com: Permission denied (publickey).

Usually means the SSH key in your workflow (secrets.DEPLOY_KEY) isn’t being read correctly, it might be invalid, misformatted, or not actually needed.

If you’re just pushing changes back to the same repository, you don’t need to set up an SSH key at all. GitHub Actions already provides a built-in GITHUB_TOKEN that can handle authentication safely.

If your workflow needs to push to another repository, then you’ll need to create and add a proper deploy key:
Generate a new key locally (ssh-keygen -t ed25519 -C "github-actions").
Add the public key to the target repo’s Deploy Keys (with “Allow write access”).
Add the private key to the current repo’s Secrets as DEPLOY_KEY.
Double-check that the private key starts with BEGIN OPENSSH PRIVATE KEY and doesn’t have extra spaces or blank lines.

[Gameking1happy]

if i push without a key branch rules block it

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬