Error with deploy_key #339
Assignees
Labels
Comments
|
In my side, I could deploy to protected branches with github_token. Log: https://github.com/peaceiris/hugo-theme-iris/actions/runs/125917906/workflow |
|
Also, there are no problems to deploy to protected branches with a Log: https://github.com/peaceiris/hugo-theme-iris/actions/runs/125905893/workflow - name: Deploy
uses: peaceiris/actions-gh-pages@v3
with:
deploy_key: ${{ secrets.ACTIONS_DEPLOY_KEY }}
publish_dir: ./exampleSite/public
|
|
I'm pretty sure your actions is working on your side. But it is not working on my package, and the README and the log are not enough for debugging my problem. I tried moving to the GITHUB_TOKEN, and enable the permission for force pushing. Still obtain an error in the final push. The complete log in the following lines. Moreover, do you have figured out WHY the deploy_key is not read from the action? I shared with you the log in the first message, but you did not address my question. 👉 Click to expand log (folded by @peaceiris) |
I mentioned in this image about this in the following image. You have two cases:
|
And, I found that your stale gh-pages branch which was deployed two years ago. I do not know the spec of stale branches. Maybe we have no permission to push to those branches with an auto-generated GITHUB_TOKEN. If you can, how about deleting the gh-page branch and deploying it again?
|
|
GitHub Actions runner returns this error, not actions-gh-pages.
|
|
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. |
|
That was a random test, with the hope that the variable name has been changed in some version but the README was not updated. It failed. I put again the To address to other points you raised (You forgot to add your private key as a secret variable to the secrets tab/You are using the wrong variable name instead of the variable name you added): I also tried to push manually on the branch (now is not a stale branch anymore), but the action still have issues. |
And again, I read the README at least a couple of time, as well as many issues that are already closed. |
OK. Thank you. I forked your repo and tried to deploy your site and succeed in my case. https://github.com/peaceiris/EZyRB/actions/runs/126011347/workflow Could you try to deploy another branch like - name: Deploy
uses: peaceiris/actions-gh-pages@v3
with:
deploy_key: ${{ secrets.DEPLOY_PRIVATE_KEY }}
publish_branch: gh-pages-test
publish_dir: ./docs/build/html |
|
Deployment with Enable branch protection to the
|
|
Restart with new secret, new key and new action (I copied yours) and still fail. And still unable to understand the error. Can you provide a way to individuate the problem, instead of replicating things until they work? |
|
The actions runner on your repo seems to have something problem with parsing inputs. (missing the This log was dumped by github actions runner. Maybe we need to report this problem at actions/runner or GitHub support... (I will do it) |
|
That's my point from the beginning: the variable Another test I did is changing the version of the action (v3 -> v2) changes the error (with v2, the variable |
|
Very very sorry... Now, I found that you are trying it on a pull-request from a forked repo. The As GitHub Actions spec, for the Please run your job on a |
|
For more details: About permissions for the GITHUB_TOKEN: Authenticating with the GITHUB_TOKEN - GitHub Help About secrets: Creating and storing encrypted secrets - GitHub Help
|
|
OK. I will enhance our warning message when this action runs on a forked repo. All users do not know the spec of GitHub Actions' secrets. I'm very sorry for taking a long time for this. As a long-service user, I should have noticed your event triggered by a forked repo at first... |
peaceiris
added a commit
that referenced
this issue
Jun 7, 2020
Please read the latest GitHub Actions official documentation and learn about the basic spec and concepts cf. #339
peaceiris
pushed a commit
that referenced
this issue
Jun 7, 2020
Please read the latest GitHub Actions official documentation and learn about the basic spec and concepts cf. #339
|
No problem at all! The important is having found the problem. Sorry for the little mess, I was not aware of such limitations related to PR. |
I'm happy to hear that!
No problem. We can make the log more friendly. After I will improve the warning message for execution on a forked repository, this issue will be closed. Thank you for using this action and for asking me about this! |
I will work on this at #359. Thank you. |
Closed
5 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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/htmldirectory to thegh-pagesbranch. Since the branch is protected, I guess thegithub_tokenis not enough (I got some permission error while pushing) then I'm trying to use thedeploy_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_keyvariable, gettingAction failed with "not found deploy key or tokens".The action log before error is:
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.
The text was updated successfully, but these errors were encountered: