ci: run checks in weekly lockfile update workflow #1930
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
PRs created by the weekly lockfile update workflow use
GITHUB_TOKENviapeter-evans/create-pull-request. GitHub intentionally does not triggeron: pull_requestworkflows for PRs created this way (to prevent recursive workflow loops), so the CI workflow—and itsall-greenjob—never runs, blocking merge.Solution
Add
workflow_dispatchto the CI workflow trigger, then dispatch it from the lockfile update workflow after creating the PR. GitHub explicitly exemptsworkflow_dispatchfrom theGITHUB_TOKENevent suppression, so CI runs on the PR branch HEAD commit and satisfies the required status check naturally.Changes
main.yml: Addworkflow_dispatchtrigger (no inputs needed—checkout defaults to the dispatched ref).weekly-lockfile-update.yml: After creating the PR, rungh workflow run main.yml --ref weekly-lockfile-updateto trigger CI on the PR branch. Remove the inlinechecksandall-greenjobs (no longer needed).shared.yml: Revert therefinput added previously (no longer needed since CI runs throughmain.ymlon the correct ref).AI Disclaimer