-
Notifications
You must be signed in to change notification settings - Fork 766
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
Set output cache-hit
to indicate if cache was hit
#275
Set output cache-hit
to indicate if cache was hit
#275
Conversation
Hello @schuenadel. Thank you for your pull request. Could you please add check that matchedKey and primaryKey are equal, because for now the cache can hit for the restore key. |
Thanks, that makes sense. I misunderstood the return value of |
@dmitry-shibanov Is there anything else needed to get this merged? Asking because I don't have the rights to merge. |
Hello @schuenadel. Sorry for the late response. Could you please sync with the main branch ? |
👍 Just did that |
Cache hit was being used as stated in this pr actions#275. However, it was not included in the outputs of the action. It did not cause any mayor issues, but if you were to lint the workflows, then an output not defined error would pop up. This Commit just adds the output to the list. Nothing more
Description:
Add the
cache-hit
output to be able to execute later steps depending on if the cache was hit like it is possible with actions/cache. Like described here: https://github.com/actions/cache/tree/main#Skipping-steps-based-on-cache-hitRelated issue:
NoneEdit: Later this issue came up, which is addressed here: #306
Check list: