Skip to content

Say what actually restarts the checks after a refresh #77

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ivanvyd merged 1 commit into from
Aug 14, 2026
Merged

Say what actually restarts the checks after a refresh #77

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion .github/workflows/refresh-lock-files.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <n> && gh pr reopen <n> # same effect, no extra commit

Verified on Healthie.NET#62 and LakeWright.NET#75.
NOTE