question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error with deploy_key

See original GitHub issue

Note that an issue which does not follow the template will be closed silently.

Check list before opening this issue

Describe your question

Trying to push the docs/build/html directory to the gh-pages branch. Since the branch is protected, I guess the github_token is not enough (I got some permission error while pushing) then I’m trying to use the deploy_key. I already added the private key on repository secrets and the public one to the deploy keys. Unluckily, the action seems not reading the deploy_key variable, getting Action failed with "not found deploy key or tokens".

The action log before error is:

Run peaceiris/actions-gh-pages@v3 with: publish_dir: ./docs/build/html publish_branch: gh-pages allow_empty_commit: false keep_files: false force_orphan: false enable_jekyll: false disable_nojekyll: false env: pythonLocation: /opt/hostedtoolcache/Python/3.6.10/x64 Dump inputs [INFO] : true [INFO] PublishBranch: gh-pages [INFO] PublishDir: ./docs/build/html [INFO] ExternalRepository: [INFO] AllowEmptyCommit: false [INFO] KeepFiles: false [INFO] ForceOrphan: false [INFO] UserName: [INFO] UserEmail: [INFO] CommitMessage: [INFO] FullCommitMessage: [INFO] TagName: [INFO] TagMessage: [INFO] EnableJekyll (DisableNoJekyll): false [INFO] CNAME:

Link to your contents

Additional context

Already check the Github status, since I’ve seen many problem related (#319) with the Github servers, but during my tests the status was always fine.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:21 (15 by maintainers)

github_iconTop GitHub Comments

1reaction
ndem0commented, Jun 9, 2020

No problem at all! The important is having found the problem. I managed to trigger the action when a new tag is pushed, and everything works!

Sorry for the little mess, I was not aware of such limitations related to PR.

1reaction
peaceiriscommented, Jun 5, 2020

In addition, I found that you are using invalid input name.

- deploy_token: ${{ secrets.DEPLOY_PRIVATE_KEY }}
+ deploy_key: ${{ secrets.DEPLOY_PRIVATE_KEY }}

Please read the README carefully.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error: Key already in use - GitHub Docs
Fixing the issue. Deploy keys. This error occurs when you try to add a key that's already been added to another account or...
Read more >
deploy keys blocked when user that added deploy key deleted ...
We recently upgraded to GitLab 12.4.2 and experienced issues where deploy keys are getting the following error.
Read more >
GitHub Error: Key already in use - Stack Overflow
8 Answers 8 · Try fixing your keys permission by running below command. chmod 400 KEY_PATH · If the above one didn't worked...
Read more >
How to fix GitHub's "Key is already in use" error - Seth Black
Or how to get around GitHub's "Key is already in use" error · push your code to master · SSH into prod01 ·...
Read more >
Github | Error: Key already in use | by Roy Tan - Medium
Story: Some of the git project included submodule, Github only allow a Unique deploy key. Which mean you cannot use a key for...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found