-
Notifications
You must be signed in to change notification settings - Fork 567
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
Add a new input to skip cache updates #751
Comments
Hello @ozancaglayan. Thank you for your feature request. We'll take a look on it. |
Ah, turns out I had the same idea! #762 |
Hello Everyone, Thank you for your feature request. The idea of adding a skip-cache-update option to control cache updates is valuable; however, it could increase complexity for users, and there’s a risk of missing out on potential caching benefits. Additionally, it would require maintenance and documentation updates. |
Hello Everyone, Please let us know in case of clarifications needed on the above. |
@aparnajyothi-y Please see my rationale for adding this feature in #762. |
Hello @akx, Thank you for your contribution to #762 and for sharing your thoughts on this feature request. We truly appreciate your understanding and patience, and we encourage you to continue sharing any further thoughts or suggestions you may have. |
Also remove setup-python caching hacks. Refs: actions/setup-python#807 actions/setup-python#762 actions/setup-python#751 Reverts: 662a971 89d73b1 e8ef6db f65666c
Description:
When this action is used with caching enabled, PRs and non-main branches creates new cache artifacts which may be overwhelming. This can be mitigated if something like
skip-cache-update: bool
option is added and users define it asfalse
if the action runs in a branch that is notmain
. This would skip the post stage of the action to effectively cancel the cache pushing.The text was updated successfully, but these errors were encountered: