Replies: 1 comment 1 reply
-
Hey, @lkraav! No activity is being forced on you. This is how the feature works to solve the problems of the majority of Turborepo users asking for this feature. You may want to take a look at the documentation for prune to better understand the problem this feature is meant to solve: https://turbo.build/repo/docs/handbook/deploying-with-docker That said, I've marked this request as accepted! It's low effort for us, sounds like a place where we can provide some extra utility for users, and satisfies a use case that I believe we've seen an ask for before (although I can't locate it at the moment). We'll get this out at some point soon! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
My current Docker build relies on manually maintained workspace lockfiles.
I'd like to replace this with automatic pruned lockfile generation, just like
turbo
suggests.I don't feel I need any further separate
out-dir
, or source copying. "Minimal amount of work" here AFAICS is just getting the lockfile.Why does
turbo
currently force all this other activity on me?Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions