-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Documentation: File ownership and permissions #512
Comments
This issue is stale because it has been open for 365 days with no activity. Leave a comment to avoid closing this issue in 5 days. |
As far as I can tell from a quick browse, this is still an issue. 👋 |
This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days. |
As far as I can tell from a quick browse, this is still an issue. 👋 |
This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days. |
If this had been fixed, I think a comment would have been made about it. |
This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days. |
Presumed unfixed. |
Problem
Neither the general workflow documentation nor this repo's README mention file ownership or permissions at all, but these things can cause this action to fail, see #133.
Suggestion
The documentation should specify the assumptions / prerequisites / requirements to successfully cache a file. Does it need to be owned by a particular user? Which user? Does it need to be readable by everyone? Is there a way to make this action work with all files regardless of their ownership and permissions?
This would help to ensure that users who follow the action's instructions end up wtih a working workflow instead of a broken one.
Note that the documentation for Docker actions says this:
... so some actions will run as root. The documentation should discuss best practices for how to ensure that root-owned files created by such actions can be cached.
The text was updated successfully, but these errors were encountered: