GitHub PR has no assignee #36212
Unanswered
uh-toby
asked this question in
Request Help
Replies: 1 comment 6 replies
-
A 404 response is not something which a client should immediately retry at the http layer. This seems like a GitHub bug, maybe a race condition between DB replicas or something like that. In theory renovate could try to remember this failure and retry adding assignees on a later run, but is that code that you'd be willing to contribute yourself or sponsor? This seems like a low priority edge case |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
A Mend.io-hosted app
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
Hi team,
We've had a few PRs created by Renovate recently without an assignee. From the logs it looks like the API call to Github failed with a 404. That seems fine - sometimes requests fail - but I'm surprised that there was no retry either in the initial build that created the PR or future builds that touched the PR.
Is it possible to retry adding PR assignees?
Is it possible to get notified when a failure happens so we can add an assignee?
Kind regards,
Toby
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions