support: ssh-agent error when using two deploy actions in one workflow

[biodranik]

Checklist

• I am using the latest version of this action.
• I have read the latest README and followed the instructions.
• I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your question

I'm getting the following error in the second deploy action when using two deploy actions in the same workflow (to deploy hugo multilingual site to two different domains/repositories):

Workflow file:

      - name: Deploy to site.com
        uses: peaceiris/actions-gh-pages@v3
        with:
          deploy_key: ${{ secrets.ACTIONS_DEPLOY_KEY_EN }}
          external_repository: site/site.com
          publish_dir: ./public/en
          user_name: My Name
          user_email: my@email
          publish_branch: master
          cname: site.com

      - name: Deploy to site.de
        uses: peaceiris/actions-gh-pages@v3
        with:
          deploy_key: ${{ secrets.ACTIONS_DEPLOY_KEY_DE }}
          external_repository: site/site.de
          publish_dir: ./public/de
          user_name: My Name
          user_email: my@email
          publish_branch: master
          cname: site.de

Relevant links

Public repository:
YAML config:
YAML workflow:

Relevant log output

Run peaceiris/actions-gh-pages@v3
[INFO] Usage https://github.com/peaceiris/actions-gh-pages#readme
Dump inputs
Setup auth token
  [INFO] setup SSH deploy key
  /usr/bin/chmod 700 /home/runner/.ssh
  [INFO] wrote /home/runner/.ssh/known_hosts
  /usr/bin/chmod 600 /home/runner/.ssh/known_hosts
  [INFO] wrote /home/runner/.ssh/github
  /usr/bin/chmod 600 /home/runner/.ssh/github
  [INFO] wrote /home/runner/.ssh/config
  /usr/bin/chmod 600 /home/runner/.ssh/config
  unix_listener: cannot bind to path /tmp/ssh-auth.sock: Address already in use
  Error: Action failed with "Command failed: ssh-agent -a /tmp/ssh-auth.sock
  unix_listener: cannot bind to path /tmp/ssh-auth.sock: Address already in use
  "

Additional context.

No response

[XiGou]

I am stucking on this issue, and I think use two action is a simple solution to this.
Although it is wasting compute resource.

[larshp]

I ran into the same problem

worked around by running killall ssh-agent