Permission denied
See original GitHub issueWhen using actions/checkout@v1
, I receive the following error from this action:
Publish gh-pagess
Deployment Failed ❌
Run JamesIves/github-pages-deploy-action@releases/v3
Checking configuration and starting deployment… 🚦
Deploying using Access Token… 🔑
Configuring git…
Git configured… 🔧
Starting to commit changes…
##[error]The deploy step encountered an error: The process '/usr/bin/git' failed with exit code 128 ❌
Deployment Failed ❌
If I switch to actions/checkout@v2
, everything works fine. However, that breaks several other actions I use, and it’s not feasible to upgrade them all at this time.
Shouldn’t this lib be backwards-compatible with both? If not, can I downgrade to a version of it that is/which one would that be?
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
How to resolve the "Permission Denied" error in Linux
While using Linux, you may encounter the error, “permission denied”. This error occurs when the user does not have the privileges to make...
Read more >How to fix 'permission denied' error in Linux? [Solutions]
What is Linux Permission Denied Error? This type of error will occur whenever you run a command for which you do not have...
Read more >How to Fix Shell Script Permission Denied Error in Linux
To fix the permission denied error in Linux, one needs to change the file permission of the script. Use the “chmod” (change mode)...
Read more >Function Compute:What can I do if the "permission denied ...
When I develop a function on an on-premises machine that runs the Windows or macOS operating system, the executable file is normally executed...
Read more >Permission denied in Mac Terminal? Try this fix - MacPaw
If you use Terminal to execute commands, you may come across a 'permission denied' error. Here's how to fix it.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
To add to the conversation am getting the same error with a new repo
Build is here: https://github.com/csi-lk/csi.lk/runs/571098491?check_suite_focus=true
Workflow: https://github.com/csi-lk/csi.lk/blob/537663b7611341e35b4a9e78ced53778cbb63eef/.github/workflows/master.yml
I’ll start trying to debug see where I get
EDIT: nevermind I spelt my secret name wrong, got it working fine
You are using the GitHub token in the wrong param, change
ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}
toGITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
. The action builds a git path but they are slightly different depending on the token you use.Please open an issue if you’re experiencing any further issues.