-
Notifications
You must be signed in to change notification settings - Fork 77
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
RTD: Rename YAML file #1078
RTD: Rename YAML file #1078
Conversation
I still do not see the RTD job here. Could be the webhook is broken but I cannot see the GitHub admin settings here. On RTD site, it is getting Error 400 . |
Webhook is still enabled, but is showing the error that 400 is happening on the RTD side. BTW, there is still a travis web hook--not using that now are we? Should we delete it? It's showing invalid HTTP response 503. |
You do not need Travis CI or Appveyor CI webhooks. You do, however, need to fix the ReadTheDocs webhook. I couldn't fix it from the RTD side. What is it saying on the GitHub side? |
"Last delivery was not successful. Invalid HTTP response: 400." |
Let me poke around the RTD side... |
Is it complaining about invalid token on GH side? |
Shows "passing" on RTD side. |
Not that I can see anywhere. |
There is no secret in the secret box, however |
Hmm why is it not JSON? |
I just kicked off a build on RTD of "latest". Double-checked that it is the correct SHA. It used the command "cat .readthedocs.yml" and successfully completed the build. So I don't think the file extension is the issue... |
Should I try switch to JSON? |
OK closing this PR then.
Doesn't hurt at this point. 😅 |
Ok, I rebased #1076 and force pushed it. Let's see what happens... |
Still getting a 400 code from RTD... |
Looks like it is still failing. There is a message on the RTD integration page for the webhook: This integration is not managed by Read the Docs currently. If this integration is not functioning correctly, you can try re-syncing it. Otherwise you'll need to update the configuration on your repository. You can use the following address to manually configure this webhook. To manually configure this webhook with your provider, use the following information... |
Ah, there was a secret there--I have pasted this into the github side. I'll try force pushing #1076 again. |
On the RTD side, for the HTTP 400 failures, it is showing the following message: {
"detail": "Payload not valid, invalid or missing signature"
} |
Under Integrations/Exchange--can you see it? |
Hmmm, thinking I might have to try the solution here... |
Might as well give that a try. Good luck! |
I think this is required for RTD to build now.