Add cache-prefixing #1169
Open
Add cache-prefixing #1169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ccoVeille
reviewed
Aug 2, 2024
Co-authored-by: ccoVeille <[email protected]>
Co-authored-by: ccoVeille <[email protected]>
|
I am hitting similar issue but this time it is because I have couple of runners working on the same VM. In this situation the user (under which the first runner operates) creates the folder and file and remains owner preventing other runners (running under different context) to have access to the tmp folder. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This changes allow the state saved to the global action cache to be stored with a prefix. Useful as
_stateis not a unique name and multiple workflows could save the cache as_state. Also useful as you currently cannot use this action twice for independent runs as the runs would pick up the same state. With this change, it is possible to have one run close all PRs with labelxafter 7 days and another run close all PRs except those with labelxafter 10 days.Also updated the README.md to show proper permissions needed.
Related issue:
#1137
Please also look into merging PR #1152 as this isn't necessarily useful if caching isn't 100% fixed.
Check list: