From 36edd5cb86cf6700fd5e8e73c86587a0b4fd2078 Mon Sep 17 00:00:00 2001
From: Pimcore Deployments <deployments@pimcore.com>
Date: Wed, 12 Aug 2026 12:56:43 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=94=84=20synced=20file(s)=20with=20pimcor?=
 =?UTF-8?q?e/workflows-collection-public?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 .github/workflows/repo-guardrails.yml | 28 +++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 .github/workflows/repo-guardrails.yml

diff --git a/.github/workflows/repo-guardrails.yml b/.github/workflows/repo-guardrails.yml
new file mode 100644
index 0000000..2d63e2f
--- /dev/null
+++ b/.github/workflows/repo-guardrails.yml
@@ -0,0 +1,28 @@
+name: Repo Guardrails
+
+# Thin, generic trigger for the REPO-level guardrails. All logic lives in the
+# central collection pimcore/workflows-collection-public. This file names no
+# guardrails, so it is identical across every repo and only needs editing if a
+# new event type or token is introduced there.
+#
+# Sibling of pr-guardrails.yml, which covers the pull-request guardrails.
+#
+# Managed centrally: this file is synced from
+# pimcore/workflows-collection-public (.github/sync-templates/repo-guardrails.yml).
+# Edit it there, not here.
+
+on:
+  issues:
+    types: [opened]
+
+concurrency:
+  # One lock per issue. Never cancel in progress: each run acts on a distinct
+  # issue, so a newer run must not abort an older one mid-decision.
+  group: repo-guardrails-issue-${{ github.event.issue.number }}
+  cancel-in-progress: false
+
+jobs:
+  guardrails:
+    uses: pimcore/workflows-collection-public/.github/workflows/parent-repo-guardrails.yml@main
+    secrets:
+      MEMBERSHIP_GUARD_TOKEN: ${{ secrets.MEMBERSHIP_GUARD_TOKEN }}