-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GITHUB PAGES - Deploy Issue #3887
Comments
I have fixed issue Deploy in local machine to GIT PAGES. Change in deploy.js BUT how to fix in GitHub Action Deploy? |
Hi, You can either submit a PR with your change, or use patch-package to temporarily patch your issue with Docusaurus in your own repo. Not sure yet, but this code works for many users, so I think it's strange if it fails only for you. Have you actually replaced the github username with your real one? You are not supposed to run |
Note: I added more logs to the deploy command recently. It's not released yet but if you use docusaurus@canary you should get the new code running locally |
I am receiving the same error in my repository. I followed the steps from the docs for the SSH key. Is this a bug in Docusaurus or am I doing something wrong? EDIT: I didn't figure out the solution but I set up an alternative workflow which seems to be working. |
@ashu231083 @OverloadedOrama apparently this was fixed in #4263, so I'm going to close this issue. But feel free to write about deployment issues if they arise. |
🐛 Bug Report
(A clear and concise description of what the bug is)
Have you read the [Contributing Guidelines on issues]fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Error: Error: git clone failed
at runDeploy (/home/runner/work/xxxxxx/xxxxxx/xxxxxx/node_modules/@docusaurus/core/lib/commands/deploy.js:86:19)
Error: Process completed with exit code 1.
To Reproduce
The text was updated successfully, but these errors were encountered: