From 1b9ed847c3cd3ea1ee8abaff530629034e69ba32 Mon Sep 17 00:00:00 2001 From: Ben van Breukelen Date: Mon, 12 Oct 2026 18:30:13 +0000 Subject: [PATCH] fix: never run the settings workflow in a fork settings.yml applies this repository's own settings. In a fork it would apply them to the fork on every push, every day on the schedule and on a manual run. The job now runs only in 030/settings-action. It checks github.repository rather than github.event.repository.fork, because a schedule event has no repository in its payload. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/settings.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/settings.yml b/.github/workflows/settings.yml index 3cbb2a3..62abf2a 100644 --- a/.github/workflows/settings.yml +++ b/.github/workflows/settings.yml @@ -11,6 +11,9 @@ permissions: contents: read jobs: settings-action: + # Only 030/settings-action applies its own settings, never a fork. Not + # github.event.repository.fork: a schedule event has no repository. + if: github.repository == '030/settings-action' runs-on: ubuntu-24.04 steps: # yamllint disable rule:line-length