Skip to content

Add the 'always-cache' option #570

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

Closed
wants to merge 1 commit into from
Closed

Conversation

kminehart
Copy link

Description:
The always-cache option will always update the cache, even in the event of a cache hit. This is particularly useful for larger projects with a lot of unit tests and a high volume of changes.

Related issue:
#569

Check list:

  • Mark if documentation changes are required.
  • Mark if tests were added or updated to cover the changes.

@kminehart kminehart requested a review from a team as a code owner March 11, 2025 15:02
@kminehart
Copy link
Author

Ah. I just tested this and realized that this won't work; it will fail to save the cache with a key that already exists, and @actions/cache has no function to delete or overwrite a cache key.

@kminehart kminehart closed this Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant