Changes from #522 don't appear on deployed docs(?)

[penelopeysm]

The relevant folders aren't in the gh-pages branch either. Quite stumped by this one.

The relevant action ran: https://github.com/TuringLang/docs/actions/runs/11002876308/job/30550755506

Force-pushing changes...
/usr/bin/git push --force ***github.com/TuringLang/docs.git github-pages-deploy-action/6quo49l0c:gh-pages
To https://github.com/TuringLang/docs.git
   9fb410c..e9b6e93  github-pages-deploy-action/6quo49l0c -> gh-pages
Changes committed to the gh-pages branch… 📦

However I don't see commit e9b6e93 anywhere on the branch history.

In fact 9fb410c doesn't seem to exist either.

[penelopeysm]

It's a spectacularly impressive race condition :/

(1) I pushed to #522 which triggered this preview workflow: https://github.com/TuringLang/docs/actions/runs/11002874097/job/30550749595

(2) Then I merged it into master which triggered this build workflow: https://github.com/TuringLang/docs/actions/runs/11002876308/job/30550755506

Unfortunately, I think (2) completed before (1), so the files on the gh-pages branch were overwritten by (1).

This should be solved (at least this time round) by rerunning the build workflow (2).

[penelopeysm]

We could probably prevent this from happening in the future by adding cancel-in-progress to the workflows.

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs