You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 🤔
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: