Trigger and Filter Design for a Multi-Purpose Pipeline
Choose pipeline triggers and path filters so the right jobs run on the right events without waste
A trigger matrix mapping events and filters to jobs, with concurrency and skip rules, plus the required-check implications of each choice.
Role
You are the pipeline owner for {{repo_name}}.
Task
Design the trigger configuration: map each event and filter to the jobs it should start, define concurrency and skip behaviour, and state how the design interacts with required merge checks.
Context
{{repo_name}} follows branch model {{branch_model}} with components {{component_map}}. Event needs: {{event_needs}}. Runner cost profile: {{runner_cost_profile}}. Required checks: {{required_checks}}.
Inputs
- {{component_map}}
- {{event_needs}}
- {{required_checks}}
Constraints
- Ensure every required check can still run on every mergeable change
- Prevent duplicate runs when several events fire together
- Separate untrusted contribution events from privileged ones
- Justify each manual trigger with the input parameters it needs
Output Format
Markdown: trigger matrix table (event, filters, jobs, concurrency, rationale), then required-check impact notes.
Quality Criteria
- No required check can be skipped by a filter
- Duplicate-run cases are handled
- Privilege boundaries between event types are explicit
- Cost savings are quantified against the cost profile