Skip to content

Conversation

@maxisbey
Copy link
Contributor

@maxisbey maxisbey commented Jan 22, 2026

Problem

PRs created by the weekly lockfile update workflow use GITHUB_TOKEN via peter-evans/create-pull-request. GitHub intentionally does not trigger on: pull_request workflows for PRs created this way (to prevent recursive workflow loops), so the CI workflow—and its all-green job—never runs, blocking merge.

Solution

Add workflow_dispatch to the CI workflow trigger, then dispatch it from the lockfile update workflow after creating the PR. GitHub explicitly exempts workflow_dispatch from the GITHUB_TOKEN event suppression, so CI runs on the PR branch HEAD commit and satisfies the required status check naturally.

Changes

  • main.yml: Add workflow_dispatch trigger (no inputs needed—checkout defaults to the dispatched ref).
  • weekly-lockfile-update.yml: After creating the PR, run gh workflow run main.yml --ref weekly-lockfile-update to trigger CI on the PR branch. Remove the inline checks and all-green jobs (no longer needed).
  • shared.yml: Revert the ref input added previously (no longer needed since CI runs through main.yml on the correct ref).

AI Disclaimer

PRs created by the weekly lockfile update workflow use the default
GITHUB_TOKEN via peter-evans/create-pull-request. GitHub does not
trigger pull_request workflows for PRs created this way, so the CI
workflow (and its all-green job) never runs, blocking merge.

Fix by having the lockfile update workflow call shared.yml directly
after creating the PR, producing its own all-green status check.

Changes:
- Add optional ref input to shared.yml for explicit checkout control
- Run shared checks against the weekly-lockfile-update branch
- Gate checks on a PR actually being created
- Add all-green job matching the required status check
@maxisbey maxisbey closed this Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants