Add PR Guardrails trigger workflow#31
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adopts the org-wide PR guardrails (linked-issue requirement + Dev-Team membership bypass + CI gate) per pimcore/service-operations#1016.
Thin, generic trigger identical to the template in payment-provider-payu — it calls
parent-pr-guardrails.yml@mainwithsecrets: inherit. The three guardrail tokens are org-level secrets with all-repository access, so no per-repo wiring is needed.Note: the guardrail activates for PRs opened after this merges (
pull_request_targetruns the base-branch workflow definition), so this PR does not exercise it.