Slow repository clone, slow CI tasks

[adamziel]

It takes over a minute to clone the repository in GitHub actions because there's so much git data to download.

A good part of that are the stale .wasm and WordPress builds. Let's rewrite the history to remove them – they're not that useful. This tool could help:

https://rtyley.github.io/bfg-repo-cleaner/

In addition, moving that data to GitHub releases would also be of huge help – this is tracked in #58

[dmsnell]

are we not doing a shallow clone in CI? we shouldn't need more than the current HEAD, so instead of rewriting history I would imagine we can just ignore it

[adamziel]

Oh, hm, yeah isn't that a good point? I wonder what takes so long here, then: https://github.com/WordPress/wordpress-playground/actions/runs/5143790977/jobs/9259248772

[adamziel]

Oh, I guess it's just the repo as stands today is 500MB+. That makes it easier, though. We can just move a bunch of built assets to GH releases.

[dmsnell]

it may be fetch-depth: 0 causing it to grab everything. the default is a shallow clone. you can try removing the with: params and see if that fixes it.

[adamziel]

Haha that was it. The inverse optimization. Nx also needs trunk, though, to run tasks only on the affected projects, so I'm trying to figure that out.

[dmsnell]

it needs the ref trunk? you can do a manual git fetch --depth=1 origin/trunk I think, or something like that

[adamziel]

Yay, it worked! The workflows are now separated and this issue isn't a problem after all: #487