-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
"Failed to import project" error is not clear #1757
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
Comments
The suggestion won't help, as there is no What's your project name? |
You mean in ula-docs |
No, you're RTD project name. |
Pardon? RTD? |
Your Read the Docs project name, I can't help any further without looking at the project configuration. |
Unfortunately this issue was critical for me and I could not wait, so I use other solution now, but I wanted you to know for future customers. |
I am with the same problem. @Serhioromano, you didn't show your project configuration for @agjohnson help us. And, what you did to solve the problem? @agjohnson, which file you need to see to help me? I am new with RTD. |
I had this problem and the cause was a typo in the repo url. It appears that "Failed to import project" is returned for failed repo pulls. Makes sense in retrospect, but a more straightforward error message would help. |
I had no longer that file by the time I was asked for it.
I am using Mkdocs instead. Completely different solution. |
@reece I need to know the name of, or link to, your project on RTD, to be able to see your configuration |
@agjohnson I should have been clearer. I had the same error as the OP, but discovered that the cause was my own typo in the URL. When I fixed the typo, everything worked fine. In my case at least, the only outstanding issue that "Failure to import project" is not as transparent as, say, "Could not clone or update repo from https://...". While you're at it, you might offer a help message that suggests trying on the command line and including a copy-pastable command line (e.g., "git clone https://..."). |
Very good guys! Now you solved my problem. Thank you. I put my docs folder somewhere inide a repo and I though that I should all the path in link. I was wrong. Thank you. |
I set up everything like it is in docs and on screencast. I use Bitbacket. I push my docs that are built locally no problems to bitbuket. It is public repo I can see source as public user. I set up Service hook as well, but even if I trigger build manually it always gives me this error
I read FAQ but I am not sure i understand if suggestion
is correct for my case. And anyway there is not link to read about
requirements.txt
configuration and how to configure it.The text was updated successfully, but these errors were encountered: