From 316ee76a2913066f8ccd86d27fdf7b17dabaff48 Mon Sep 17 00:00:00 2001 From: Matysh Date: Thu, 13 Aug 2026 16:21:33 +0300 Subject: [PATCH] fix: repair the line continuation in the failure handler The step that comments on the issue when a review run dies carried a literal backslash instead of a line continuation, so gh received four arguments and --repo ran as a command of its own. The handler for failures would itself have failed, silently, and only when something had already gone wrong. bash -n does not catch this: the syntax is valid, the meaning is not. Checking run blocks now also means looking for a doubled backslash at end of line. Issue: #114 User-Visible: no --- .github/workflows/process.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/process.yml b/.github/workflows/process.yml index f07397a7..1f197671 100644 --- a/.github/workflows/process.yml +++ b/.github/workflows/process.yml @@ -337,5 +337,5 @@ jobs: Если вердикт выше всё же опубликован — сбой произошёл после него. Перестановку метки в этом случае выполняет чат обслуживания или владелец, но не автор задачи: автор не толкует вердикт о своей же работе. EOF - gh issue comment "${{ github.event.issue.number }}" \\ + gh issue comment "${{ github.event.issue.number }}" \ --repo "${{ github.repository }}" --body-file /tmp/failure.md