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
I have two separate workflows (I simplified the details as much as possible for brevity):
ci runs on push: trigger and creates a cache key key-${{github.sha}}
pr-checks runs on pull_request: trigger (with synchronize included) and tries to read key key-
My understanding is that, pr-checks should be able to read from the cache, even if in case of synchronize event it would get the cache corresponding to the previous commit sha that was cached.
However the pr-checks always fails with cache not found for key ..., even though if check on Github's UI, valid cache keys for that branch exists.
Is this expected? Does it have something to do with the scope of the cache? (I wouldn't expect it, since the cache was created in the scope of let's say feature-branch-1, and the PR ref is also feature-branch-1)
The text was updated successfully, but these errors were encountered:
Having a similar issue. I have two on pull_request workflows. One that runs when the pull request is created and one after it is merged. Even though they are for the same branch, the cache created when the pull request is created is not found in the workflow when the pull request is merged.
I have two separate workflows (I simplified the details as much as possible for brevity):
ci
runs onpush:
trigger and creates a cache keykey-${{github.sha}}
pr-checks
runs onpull_request:
trigger (withsynchronize
included) and tries to read keykey-
My understanding is that,
pr-checks
should be able to read from the cache, even if in case ofsynchronize
event it would get the cache corresponding to the previous commitsha
that was cached.However the
pr-checks
always fails withcache not found for key ...
, even though if check on Github's UI, valid cache keys for that branch exists.Is this expected? Does it have something to do with the scope of the cache? (I wouldn't expect it, since the cache was created in the scope of let's say
feature-branch-1
, and the PR ref is alsofeature-branch-1
)The text was updated successfully, but these errors were encountered: