From f45adceef0f4b90049af8a0adb05df4ba27fb723 Mon Sep 17 00:00:00 2001
From: grabowski <berwn@buildfor.life>
Date: Wed, 1 Jul 2026 11:51:59 +0700
Subject: [PATCH] Bound deploy SSH step to 5m so a hung session fails fast

A leftover child process from npm ci/build can keep the SSH
session's file descriptors open even after the remote script
exits, leaving the Action step hanging indefinitely with no
useful signal -- the actual deploy work (build, restart, health
check) normally finishes in well under a minute.
---
 .gitea/workflows/deploy.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml
index 862eee3..bdf804e 100644
--- a/.gitea/workflows/deploy.yml
+++ b/.gitea/workflows/deploy.yml
@@ -15,6 +15,7 @@ jobs:
           username: ${{ secrets.DEPLOY_USER }}
           key: ${{ secrets.DEPLOY_KEY }}
           port: ${{ secrets.DEPLOY_PORT || 22 }}
+          command_timeout: 5m
           script: |
             set -e