src/compile/pr_filters.rs — when PrTriggerConfig has no branches/paths (only filters), generate_native_pr_trigger returns String::new(). This cascades up through generate_pr_trigger as an empty string. The effect is that no pr: block appears in the output YAML, which falls back to ADO repo-level defaults. This is probably the right behavior (let all PRs through the native trigger, then gate via the evaluator), but it's implicit. A comment explaining this is intentional would help readers.
src/compile/pr_filters.rs — when PrTriggerConfig has no branches/paths (only filters), generate_native_pr_trigger returns String::new(). This cascades up through generate_pr_trigger as an empty string. The effect is that no pr: block appears in the output YAML, which falls back to ADO repo-level defaults. This is probably the right behavior (let all PRs through the native trigger, then gate via the evaluator), but it's implicit. A comment explaining this is intentional would help readers.