-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Is there some sort of caching happening? If so, how to clear it? #915
Comments
yes, caching is used, but it should be using the regular HTTP caching semantics, so it seems somewhat unlikely to get into a situation where a stale cache exists 🤔 |
Interesting. It may be on github's end, I'll monitor and see if I can get a useful repro |
I haven't encountered this any more, and you did answer the original question, so I think you can close this issue. Thank you for your time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So I've noticed recently that some prs are not picked up even though they are properly labeled (we use the default labels).
What they have in common is that they're all pr's that were merged very quickly by myself (usually in the frantic hours of late-night debugging)
Is there some sort of debounce/caching/rate limiting happening? (I have the github token set up as per the docs)
I understand it's not really a typical usecase, but sometimes the PR flow is too much overhead but you still want to keep nice changelogs. So if this is expected behavior that's totally fair. But maybe it would be good to document it?
The text was updated successfully, but these errors were encountered: