When checks on next fail, periodically check again incase it was a transient error #88

Closed
opened 2024-06-02 20:01:13 +01:00 by kemitix · 0 comments
Owner

Sometimes the build can fail sure to a network issue, and rerunning the checks can result in a pass. However, because this doesn't send a webhook (some forges might) the server should periodically check if the statuses change.

GitHub appears to support sending events for checks: https://docs.github.com/en/webhooks/webhook-events-and-payloads#check_run etal, so handling these events would be preferable to a scheduled timer for repos on this forge.

ForgeJo doesn't, so a scheduled timer would be needed for repos on this forge.

Sometimes the build can fail sure to a network issue, and rerunning the checks can result in a pass. However, because this doesn't send a webhook (some forges might) the server should periodically check if the statuses change. GitHub appears to support sending events for checks: https://docs.github.com/en/webhooks/webhook-events-and-payloads#check_run etal, so handling these events would be preferable to a scheduled timer for repos on this forge. ForgeJo doesn't, so a scheduled timer would be needed for repos on this forge.
kemitix added this to the Road to v1 - Forgejo & Github project 2024-07-11 19:29:18 +01:00
kemitix referenced this issue from a commit 2024-07-12 08:05:44 +01:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: kemitix/git-next#88
No description provided.