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
Previously, running an update was fairly quick, with the optimizations around using HEAD and ETag to conditionally and quickly determine if a full GET was needed.
Since the introduction of the SHA retrieval, however, things are much slower now, since we do a GH CLI call for (almost) all requests.
We should instead optimize and not retrieve the SHA if:
We have a matching ETag from request/response
We already have a SHA persisted
The text was updated successfully, but these errors were encountered:
Previously, running an update was fairly quick, with the optimizations around using HEAD and ETag to conditionally and quickly determine if a full GET was needed.
Since the introduction of the SHA retrieval, however, things are much slower now, since we do a GH CLI call for (almost) all requests.
We should instead optimize and not retrieve the SHA if:
The text was updated successfully, but these errors were encountered: