-
Notifications
You must be signed in to change notification settings - Fork 54
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
mkdocs auto deploy doesnot work. #848
Comments
Hey @vyasakhilesh - I just tested this on two of my repos, and it works OK. Note that in order to run this, you need to have at least write rights on the repo in question (you need to be able update branches). Can you double check your permissions? Also, you may have to generate a GitHub token to use as a password for this process. |
Thanks @matentzn , I was trying to do it using ssh-keys .. so do you need to include the token in the origin URL? Or simply in .github/token.txt file ? Does it ask for a username and password when update_docs tries to push code in the remote repo if you add in token.txt? |
Yes, it does ask me for username and password.. If you want to get this working with token.txt: @gouttegd I never tried this, but is there anything @vyasakhilesh needs to do specifically? |
I don’t think it would be possible to use a GitHub token for this. From what I can see, Standard @vyasakhilesh : Is your SSH setup “complicated”? Like, do you use SSH agent with forwarding, or a private key stored on a physical token that you access through GnuPG or similar? If you have a simple setup (like, a regular SSH key stored in
|
As a workaround, are there known problems with using |
@pfabry I did exactly that in the past, no problems at all. I do believe that mkdocs gh-deploy does not really create a commit though, it seems to overwrite the whole branch. At least it seems that way, see https://github.com/obophenotype/upheno/commits/gh-pages |
@vyasakhilesh I am closing this now, but if this continues to be an issue please re-open! |
While running below command from the host machine
Getting this error
The text was updated successfully, but these errors were encountered: