From 49324166f4d2cd3ef5415c5eeca1b069f2723521 Mon Sep 17 00:00:00 2001 From: Ivan Vydrin Date: Fri, 14 Aug 2026 08:32:14 +0300 Subject: [PATCH] Say what actually restarts the checks after a refresh The workflow told you to re-run the pull request's checks. There is nothing to re-run: a push made with GITHUB_TOKEN does not create a workflow run at all, so the required checks simply have no result against the new head and the PR sits BLOCKED with everything apparently green. Found by using it. Healthie.NET#62 stayed blocked with `build` and `End-to-end (browser)` absent rather than failing, and only an empty commit from a human identity started them. LakeWright.NET#75 behaved the same way, except there the held run could be approved instead. The message now gives both commands that work, and says why the obvious one does not. --- .github/workflows/refresh-lock-files.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/.github/workflows/refresh-lock-files.yml b/.github/workflows/refresh-lock-files.yml index a5c7f37..8d17c95 100644 --- a/.github/workflows/refresh-lock-files.yml +++ b/.github/workflows/refresh-lock-files.yml @@ -76,4 +76,15 @@ jobs: `--locked-mode` and a Release build. Dependabot cannot write these under central package management; see .github/workflows/refresh-lock-files.yml.' git push origin HEAD:'${{ inputs.branch }}' - echo "Pushed. Re-run the pull request's checks -- a GITHUB_TOKEN push does not." + cat <<'NOTE' + Pushed. + + The checks will not start on their own. A push made with GITHUB_TOKEN creates no + workflow run at all -- there is nothing to "re-run", which is the part that is easy + to get wrong. Start them one of these ways: + + git commit --allow-empty -m "Trigger CI" && git push # from your own identity + gh pr close && gh pr reopen # same effect, no extra commit + + Verified on Healthie.NET#62 and LakeWright.NET#75. + NOTE