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
Description:
I'd like to propose adding a new output called cache-hit (like in actions/cache) to show whether dependency cache was hit.
Justification:
Since this action utilizes caching mechanic I think it would be needed to have this meta data in output since we can't access internal steps from outside.
This would be helpful if, for example, we need add stuff to PATH if this cache was hit. Another example is when you want to do optional poetry install, because there's no lock file and poetry will first try to resolve even if deps are there.
Are you willing to submit a PR?
Yes, for sure.
The text was updated successfully, but these errors were encountered:
Hello @dhvcc. Thank you for your proposal. I think this enhancement can be implemented. If you're willing to contribute, please feel free to prepare a pull request.
Just as an addition - perhaps this type of output may be usefull in other setup-* workflows? I've checked an saw only setup-node providing the same output
Description:
I'd like to propose adding a new output called
cache-hit
(like in actions/cache) to show whether dependency cache was hit.Justification:
Since this action utilizes caching mechanic I think it would be needed to have this meta data in output since we can't access internal steps from outside.
This would be helpful if, for example, we need add stuff to
PATH
if this cache was hit. Another example is when you want to do optionalpoetry install
, because there's no lock file and poetry will first try to resolve even if deps are there.Are you willing to submit a PR?
Yes, for sure.
The text was updated successfully, but these errors were encountered: