Deletes existing .yarn/install-state.gz file
#169
Merged
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
This was mistakenly committed in the past and is not necessary. > `.yarn/install-state.gz` is an optimization file that you shouldn't ever have to commit. It simply stores the exact state of your project so that the next commands can boot without having to resolve your workspaces all over again. Source: https://yarnpkg.com/getting-started/qa#which-files-should-be-gitignored
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
arthurgousset
changed the title
.yarn/install-state.gz file.yarn/install-state.gz file
|
Why won't this file delete? Any ideas @celo-org/devtooling ? |
shazarre
approved these changes
Apr 24, 2024
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
I thought the file was deleted here: #168
It was only modified . This PR tries to delete it for good.
Tested
No, will be tested manually when deployed.
Related issues
.gitignoresettings #168Backwards compatibility
Yes
Documentation
None