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
Right now we cache GitHub API responses between audits/workflows, but there are a lot of responses that also make sense to cache between zizmor runs (e.g. a commit that isn't an impostor isn't going to become an impostor).
The text was updated successfully, but these errors were encountered:
Thinking about this more: I think almost all of the caching can be moved into HTTP middleware, since nothing else we do is really that expensive (or more precisely, so expensive that it makes sense to cache between runs).
Right now we cache GitHub API responses between audits/workflows, but there are a lot of responses that also make sense to cache between
zizmor
runs (e.g. a commit that isn't an impostor isn't going to become an impostor).The text was updated successfully, but these errors were encountered: