Sachin Patel
Sachin Patel
This actually specially happens where you have a path traversal input.
yes - dry run now includes local/remote cache status
Out of curiosity what is the full output with log verbosity increased? (-vv)
Agree this would be useful have run into this as well. To kind of work around this - we've had to introduce a status check that runs hourly that modified...
I opened https://github.com/vercel/turborepo/issues/1250 and https://github.com/vercel/turborepo/issues/1249 before seeing this - both seem related.
I am able to do this today with path spec syntax.. ``` "//#format": { "inputs": [ ":!packages/", ":!tools/", "*.js", "*.jsx", "*.ts", "*.tsx", "*.json", "*.md" ], "outputs": [] }, ```
I followed https://css-tricks.com/git-pathspecs-and-how-to-use-them/#aa-exclude. I have def noticed inconsistency on what works and what doesn't especially with comparison to ls-files.
> Extending `--dry-run=json` seems like a good idea for this. Curious about your approach of sharding it though. Sounds interesting, any plans to share snippets of it? I think this...
fyi - I have received approval to author a blog and examples. Stay tuned!
@weyert / @gsoltis here you go.. https://medium.com/@sppatel/maximizing-job-parallelization-in-ci-workflows-with-jest-and-turborepo-da86b9be0ee6 Hopefully this gives the request a little bit more meaning and substance.