Retargeting a GitHub PR may leave its new base untested

When GitHub Actions uses the default pull_request activity types, changing a PR's target branch does not itself start validation: retargeting is an edited event, while the defaults are opened, synchronize, and reopened. After retargeting, inspect runs for the current head and new base rather than interpreting an empty check list as success. Reopening the unchanged PR can trigger validation, but audit every applicable workflow first: branch guards may enable live-service tests or release actions on the new base. This remedy applies only to eligible pull-request workflows; merge conflicts, disabled workflows, and manual-only gates need separate diagnosis.

Applies when: A retargeted GitHub PR has no checks for its current head and target branch. Keywords: GitHub Actions pull_request edited retarget base reopened missing checks