Error with deploy_key
See original GitHub issueNote that an issue which does not follow the template will be closed silently.
Check list before opening this issue
- I read the latest README
- I checked Available Options
- I followed Tips and FAQ
- I tried Workflow Examples
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
- Link to your public repository: https://github.com/mathLab/EZyRB
- Link to your workflow: https://github.com/mathLab/EZyRB/actions?query=workflow%3A"Pull+Request+Docs+Check"
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:
- Created 3 years ago
- Comments:21 (15 by maintainers)
Top GitHub Comments
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.
In addition, I found that you are using invalid input name.
Please read the README carefully.