Closed jcfr closed 12 months ago
Thanks for providing detailed info :detective: I just ran into the same issue too.
Hi @jcfr can you check that you can create PRs now? This should have been a momentary problem while we are migrating all possible webhooks to have a secret (we are still in the process).
We should also have a better error message, since in this case was due to the missing secret on the integration.
@thephez looks like your webhook doesn't have a secret yet, this is because our migration hasn't hit your project yet or because you don't have a GitHub account connected. In any case, you can hit the resync webhook
button on your integration, if you have your account connected, the secret will be added automatically, if you don't, you'll need to manually update the webhook on GitHub, see https://docs.readthedocs.io/en/stable/guides/setup/git-repo-manual.html for step-by-step guide.
We will email all projects that need manual migration after we have migrated the webhooks that we can migrate automatically.
@stsewd Thanks! Is the migration expected to be completed soon?
@thephez hopefully in an hour or so,
Hmm, actually, looks like an actual regression, the header name is wrong, fix in https://github.com/readthedocs/readthedocs.org/pull/10903.
Fix should be out, but if your webhook doesn't have a secret, it won't respond to PR events, follow the step from in that case https://github.com/readthedocs/readthedocs.org/issues/10902#issuecomment-1811129965.
Automatic migration is almost done, we will email users in a bit too.
can you check that you can create PRs now?
After updating the pull-request, I confirm the ReadTheDocs build job has been successfully triggered.
GitHub incoming webhook payloads | Builds |
---|---|
Thanks again @stsewd and @thephez for the quick follow-up and updates :pray: :rocket: :100:
...In any case, you can hit the
resync webhook
button on your integration, if you have your account connected, the secret will be added automatically, if you don't, you'll need to manually update the webhook on GitHub, see https://docs.readthedocs.io/en/stable/guides/setup/git-repo-manual.html for step-by-step guide.
The webhook I'm having issues with was created before I was around so I'm not sure what method was used. In any case, resyncing it doesn't work: Webhook activation failed. Make sure you have the necessary permissions.
Is there a way to view the secret (I haven't found it) or do I need to just create a new webhook?
Edit: I created a manual webhook on another project and it worked successfully. I guess since I can't see a secret on the project mentioned above, the webhook wasn't originally configured manually. Something has happened to prevent it from working or resyncing now following the update yesterday. I'm guessing creating a new webhook for it manually is the quickest path forward. Just letting you know in case you have others that run into this issue.
@thephez maybe the RTD app doesn't have access to that organization, in that case you can follow this guide https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.
Always showing the secret can also be an improvement, so users can complete the process manually in case of an en error with permissions.
Details
Actual vs Expected Result
Looks like following the release of
10.11.0
integrating https://github.com/readthedocs/readthedocs.org/commit/55511b40ddcd6414183759db58eccc2907a7a3a8, existing GitHub integrations like the one of theslicer
project are failing to process incoming payload associated with pull-request.I wasn't able to confirm with this also applies to branch update (e.g integration into
main
)To further illustrate, here is the pull-request payload corresponding to https://github.com/Slicer/Slicer/pull/7389 where
id
andnode_id
were replaced with placeholders.Incoming GitHub Payload:
Additional information
Merge pull request from GHSA-45hq-g76r-46wv