Conversation
Collaborator
|
Thanks for the patch. What's the benefit in changing the phpunit cache location to you? |
Contributor
Author
|
This is a standard practice in all my projects
Actually, we could do the same with the |
(cherry picked from commit 9c9dc46)
3245d4c to
c397cf2
Compare
Collaborator
|
@codemasher I've rebased this branch on top of the latest changes, keeping only the changes that make sense to me. Thank you for contributing! |
This file contains hidden or 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
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.
Hey,
this PR updates the workflow runs to use the latest versions of
actions/checkoutandramsey/composer-installto stop the node.js deprecation warnings.Further I have moved the PHPUnit cache directory under
.build/.phpunit.cache(now looking at it, the leading.is a bit unnecessary) and cleaned up the.gitignore.Cheers!