nurdotnet d7ee6d12f8 ci(forgejo): fold deploy-stage into docker workflow via needs ... Forgejo Actions doesn't reliably trigger a separate workflow on `workflow_run: Docker Images succeeded` (at least on 7.0.16), so the stage deploy would never fire. Merging the deploy step into the same docker workflow as a dependent job keeps it atomic: build api, build web, then (needs: [api, web]) deploy + smoke + telegram ping.		2026-04-23 16:47:28 +05:00
..
ci.yml	ci(forgejo): retrigger after dotnet sdk 8.0.420 available system-wide	2026-04-23 16:25:08 +05:00
docker.yml	ci(forgejo): fold deploy-stage into docker workflow via needs	2026-04-23 16:47:28 +05:00
notify.yml	ci(forgejo): mirror .github/workflows to .forgejo/workflows	2026-04-23 16:19:24 +05:00