a year ago
Hello, I just updated my upstream repo that my template is using in two services. At first I used the "check for updates" in both services and updated them to latest, I then had a build error and had to push a new fix, however, since that the "check for updates" fails to find ny new commits. What can I do? I have seen this before in other project where it did not work at all when I pushed, but I have some hopes here since it did work the first time just 10 minutes ago. 🙏
0 Replies
a year ago
f40468c7-29f6-4806-9ec5-30050947b99d
a year ago
the check for updates is cached for 24 hours afaik
a year ago
cc @Faraz what would be the reason for such a long cache on that? is it an API intensive check?
a year ago
Good question. It is intensive + GH API rate limits for public repos aren't great even when authenticated.
a year ago
am i correct with the 24 hour number?
a year ago
Yes.
a year ago
would dropping that down to 12 hours be okay, or would it be worth it to instead purse alterative methods to check for updates?
a year ago
I think we could make this fetch fresh on click and the automatic fetch can remain 24h.
a year ago
best of both worlds!
a year ago
would need a limit per hour or a dead time though, check <#1177701394929680465> if you wanna know why i say that <:kekw:788259314607325204>
a year ago
That sounds good! Thanks! 🙂 today I was able to fetch the update
a year ago
Btw, aren't there some GH hooks that would work the other way around? So you don't have to poll for updates?
a year ago
This is kinda finicky as these are public repos.
a year ago
Receiving webhooks only works if the repo owner has given us access to the repo. Us being our GH app.
a year ago
Anyway, just merged a fix for this so it doesn't use the cache when manually checking. 👍
a year ago
Amazing ! 😄 thank you !!!