Now that we control how ofter river data is generated, let's do it more often. That means bumping the cron in the GitHub repo and running our consumer cron more often. The issue is that on recently uploaded modules (over say 24 hours) many of them will not have a river gauge because it' a bit harder to tell if they truly have no deps or if they just haven't been included in the calculations.
So, if we run this maybe 4-6 times per day, we'd have better insight into river position for new modules. Of course most (or all) of them will not really have anything to display on the river gauge, but there's no harm in keeping the calculated data fresh.
Now that we control how ofter river data is generated, let's do it more often. That means bumping the cron in the GitHub repo and running our consumer cron more often. The issue is that on recently uploaded modules (over say 24 hours) many of them will not have a river gauge because it' a bit harder to tell if they truly have no deps or if they just haven't been included in the calculations.
So, if we run this maybe 4-6 times per day, we'd have better insight into river position for new modules. Of course most (or all) of them will not really have anything to display on the river gauge, but there's no harm in keeping the calculated data fresh.