-
-
Notifications
You must be signed in to change notification settings - Fork 54
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
Proper caching #25
Comments
Hi @szepeviktor , I considered the caching of the vendor directory a useful feature (as long as the cache is validated against the composer.lock file). Please can you suggest an alternative method of doing this? The documentation of https://github.com/actions/cache was used when forming my opinion of caching the vendor directory (the example uses the |
I'm not able to convince you that only the cache directory should be actually cached. Composer can install packages from the cache to |
Please see this PR #26 |
This is great, thanks very much. I'll check it out and merge the PR once tested. |
Thanks. Merged #26. |
You're welcome. |
Please do not encourage users to cache vendor directory.
path: vendor/
It makes CI unpredictable.
BTW
::set-output
is unused in README.The text was updated successfully, but these errors were encountered: