Add post hook to cancel in-progress deployments if the job/workflow run ends unsuccessfully about deploy-pages HOT 1 CLOSED

This is probably even more important than I originally thought as Pages self-regulates the concurrency of in-progress deployments to one per repository + branch/ref.

As such, if you had an Actions workflow to deploy Pages with a concurrency.cancel-in-progress: true configuration, a second workflow run ("RunB") could cancel an in-progress first workflow run ("RunA"), which might leave the Pages deployment from "RunA" in-progress, but the second workflow run will outright fail because it cannot start another Pages deployment for that same branch until the previous deployment is resolved. 🔁 🔀

Failed workflow run example of that particular scenario:

Furthermore, if you never queue any "RunC" after those (or re-run "RunB"), the changes associated with "RunB" may never get deployed. 👻

from deploy-pages.