From 1ae57f7c5d383465bbb9068470f440c8f0faff24 Mon Sep 17 00:00:00 2001 From: Sluijsens Date: Thu, 23 Jul 2026 23:32:40 +0200 Subject: [PATCH] docs: leg uit hoe deploy-goedkeuring werkt in Gitea Actions Gitea Actions kent geen GitLab/Azure DevOps-achtige manual approval gate; workflow_dispatch is het dichtstbijzijnde equivalent. Co-Authored-By: Claude Sonnet 5 --- .gitea/workflows/deploy.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 940ac77..4d1414a 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -7,6 +7,10 @@ name: Build, Test and Package Release # (no automatic upload to a host yet) and only runs for manual (workflow_dispatch) runs. # Typically run on a `release/*` branch once you've manually created it for a release. # - Uploaded artifacts expire after 1 day (retention-days: 1). +# - Gitea Actions has no GitLab/Azure DevOps-style approval gate (a single job with a +# "manual" play button inside an already-running pipeline). The closest equivalent is +# workflow_dispatch: the deploy job only runs when someone presses "Run workflow" in +# the Gitea Actions UI, i.e. a one-click manual approval. on: workflow_dispatch: {}