Post

Dominik 🔮
@tkdodo.eu

@juri.dev I remember the nx docs recommend setting `fetch-depth: 0` to make nx-affected work; For us, on a relatively big monorepo, this took 1m40s on CI because it fetches all history😅. We now found out that setting `filter: tree:0` gets that down to 28s while nx affected still works 🤯

4 reposts40 likes

Louis DeScioli
@lou.descioli.com

Oh that's brilliant, thanks for posting this! This should definitely be in the docs. I bumped up against this problem at my last job with a huge repo history. I hacked together a solution that was much more brittle and lost a few days worth of time going back to fix it.

Seb ⚛️ ThisWeekInReact.com
@sebastienlorber.com

If this interest anyone, here's my analysis and benchmarks For us, blobless seems the best option, but Vercel doesn't offer it apparently 😅 github.com/facebook/doc...

github.comDocument solution to "docs last update" date being rendered incorrectly when published through Vercel · Issue #10031 · facebook/docusaurusHave you read the Contributing Guidelines on issues? I have read the Contributing Guidelines on issues. Description Setting the VERCEL_DEEP_CLONE environment variable to true through vercel's Proje...