djkotowski f210373c3e Fix Pages deploy concurrency and tag successful deploys (#237)
* Use safe concurrency pattern for Pages deploys

Switch to the group: pages, cancel-in-progress: false pattern GitHub
recommends for deploy-pages, so a superseded run is skipped before it
starts rather than killed mid-deploy, which can leave the Pages
deployment stuck in progress.

* Tag each successful Pages deploy

There is currently no record of which commits were actually deployed.
Tag the deployed commit as deploy-YYYY-MM-DD-<sha> right after
deploy-pages succeeds, giving a lightweight, always-unique history of
production deploys without introducing a formal versioning/release
scheme.
2026-07-18 16:01:31 -05:00
2025-03-16 00:55:37 -05:00
2023-05-06 22:20:45 -05:00
2024-07-01 15:42:47 -05:00
2025-04-02 12:52:32 -05:00
2023-05-08 21:38:26 -05:00
2024-06-20 13:55:37 -05:00
2023-05-06 22:20:45 -05:00
2023-05-06 23:00:50 -05:00

Dan's Personal Website deploy

Available at https://dankotowski.dev

S
Description
My personal website
Readme
3 MiB
Languages
Svelte 90.3%
HTML 4.2%
JavaScript 3.9%
TypeScript 1.4%
CSS 0.2%