We noticed that RefreshCheckRunsJob and RefreshStatusesJob both could end up being long running if there are a lot of statuses to refresh and GitHub is slow. This changes both of these jobs to re-enqueue itself once per each of the stack's last 30 commits if passed in a stack as an argument.
We noticed that
RefreshCheckRunsJob
andRefreshStatusesJob
both could end up being long running if there are a lot of statuses to refresh and GitHub is slow. This changes both of these jobs to re-enqueue itself once per each of the stack's last 30 commits if passed in a stack as an argument.