Summary

Introduce a configurable trigger delay or batch option for target branch pipelines on merged PRs, so that concurrent merges within a short time window consolidate into a single (or fewer) pipeline run(s) instead of triggering one per merge.

Current Behaviour

When multiple PRs are approved and added to the Merge Queue with high concurrency (e.g., 10), each successful merge triggers a separate target branch pipeline run. Since the Merge Queue has already validated each PR (tests passed, builds verified), these repeated target branch runs are redundant. Target branch pipelines are typically the most expensive, so triggering them back-to-back for a single "wave" of merges wastes significant build minutes.

Suggestion

Introduce a configurable trigger delay or batch option for target branch pipelines on merged PRs. When multiple merges happen within a defined time window, the pipeline would wait briefly to allow other in-flight merges to complete, then trigger once (or fewer times) rather than once per merge. This should only apply when multiple PRs are merged concurrently via the Merge Queue. Single-PR flows should remain unaffected.