Skip to content

ci: document Actions event policy needed for pull_request_target - #938

Merged
foursixnine merged 1 commit into
masterfrom
ci-pull-request-target-policy
Oct 7, 2026
Merged

foursixnine merged 1 commit into
masterfrom
ci-pull-request-target-policy

Conversation

@foursixnine

Copy link
Copy Markdown
Member

GitHub is enforcing (2026-11-02) a default Actions event policy for public repositories that blocks workflows triggered by pull_request_target unless an explicit policy allows it (see https://docs.github.com/actions/reference/security/securely-using-pull_request_target).

Without action, .github/workflows/ci.yml (which relies on pull_request_target to safely access APIKEY/APISECRET secrets while checking out PR content into a subdirectory for inspection only) would stop triggering on pull requests after that date.

Action taken:

  • Created a repository-level Actions event policy (via POST /repos/os-autoinst/opensuse-jobgroups/actions/policies) that explicitly allows push and pull_request_target, scoped to .github/workflows/ci.yml, with enforcement: active. This keeps the workflow triggering correctly both before and after GitHub's Nov 2, 2026 enforcement date.
  • Added a comment to the workflow file documenting the policy requirement, why this specific usage of pull_request_target is safe (no PR code is ever executed, only linted/inspected as data), and where to find/manage the policy.

No functional changes to workflow steps.

@foursixnine
foursixnine force-pushed the ci-pull-request-target-policy branch from 648649d to 38a1ff6 Compare October 7, 2026 08:59
GitHub is enforcing (2026-11-02) a default Actions event policy for
public repositories that blocks workflows triggered by
pull_request_target unless an explicit policy allows it. Without
action this workflow would stop triggering on pull requests.

A repository-level Actions event policy explicitly allowing
pull_request_target, scoped to this workflow file, has been created
via the GitHub REST API so the workflow keeps working after
enforcement. This commit documents why and how, for future
maintainers.

Assisted-by: GitHub Copilot Claude Sonnet 5
@foursixnine
foursixnine force-pushed the ci-pull-request-target-policy branch from 38a1ff6 to 5b23e24 Compare October 7, 2026 09:00
@foursixnine
foursixnine merged commit d294e5c into master Oct 7, 2026
6 checks passed
@foursixnine
foursixnine deleted the ci-pull-request-target-policy branch October 7, 2026 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants