-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Move fs cache location. #8126
Move fs cache location. #8126
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
9 Ignored Deployments
|
🟢 Turbopack Benchmark CI successful 🟢Thanks |
✅ This change can build |
345dbab
to
d11acea
Compare
Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
🟢 CI successful 🟢Thanks |
Never the saw the CI that happy 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Defer to @chris-olszewski on this, but I'm ok with it!
d11acea
to
f8bea45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LFG official Rustacean @anthonyshew
@chris-olszewski If I knew all it took was changing a hardcoded string, I would have done it a long time ago. If this makes me official, then #8157 makes me King Crab. |
### Description Moves the file system cache to `.turbo` as discussed in #842. ### Testing Instructions Find your favorite Turborepo of choice and run a `turbo` command twice. You should miss cache on the first run and hit cache on the second. CLOSES TURBO-3130 --------- Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
### Description Moves the file system cache to `.turbo` as discussed in #842. ### Testing Instructions Find your favorite Turborepo of choice and run a `turbo` command twice. You should miss cache on the first run and hit cache on the second. CLOSES TURBO-3130 --------- Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
### Description Moves the file system cache to `.turbo` as discussed in #842. ### Testing Instructions Find your favorite Turborepo of choice and run a `turbo` command twice. You should miss cache on the first run and hit cache on the second. CLOSES TURBO-3130 --------- Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
### Description Moves the file system cache to `.turbo` as discussed in #842. ### Testing Instructions Find your favorite Turborepo of choice and run a `turbo` command twice. You should miss cache on the first run and hit cache on the second. CLOSES TURBO-3130 --------- Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
### Description Moves the file system cache to `.turbo` as discussed in #842. ### Testing Instructions Find your favorite Turborepo of choice and run a `turbo` command twice. You should miss cache on the first run and hit cache on the second. CLOSES TURBO-3130 --------- Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
### Description Moves the file system cache to `.turbo` as discussed in #842. ### Testing Instructions Find your favorite Turborepo of choice and run a `turbo` command twice. You should miss cache on the first run and hit cache on the second. CLOSES TURBO-3130 --------- Co-authored-by: Chris Olszewski <chris.olszewski@vercel.com>
@anthonyshew What are the implications of this PR in regards to https://github.com/vercel/turbo/blob/c2fb13e3101ae2a6331453a3e925d832e52ced91/docs/pages/repo/docs/ci/github-actions.mdx?plain=1#L240 Is supplying --cache-dir=.turbo still necessary with v2 if I want github actions cache to work? I'm having a hard time understanding if this PR means "the dir is now .turbo inside <workspace_package_dir>/.turbo, so we set --cache-dir in the github actions docs beacuse we want all of the packages' cache to be in one centralized dir"? |
### Description As I see it, since the default cache location is now `<root-dir>/turbo/.cache` due to #8126, there's no longer a point in specifying the --cache-dir=.turbo as it is redundant no? ### Testing Instructions Run a GitHub actions with https://turbo.build/repo/docs/guides/ci-vendors/github-actions#caching-with-github-actionscache and see if it caches properly
Description
Moves the file system cache to
.turbo
as discussed in #842.Testing Instructions
Find your favorite Turborepo of choice and run a
turbo
command twice. You should miss cache on the first run and hit cache on the second.CLOSES TURBO-3130