Problem description
The documentation does not clearly recommend batching deployments as the pattern when many PRs/commits target a single stack in quick succession. Without this guidance, users reach for ad-hoc workarounds (e.g., manually enabling preempt / cancel-intermediate) and aren't sure they've landed on the supported best practice.
Suggestions for a fix
Add a best-practices note stating the recommendation to batch deployments for high-PR-volume stacks, what batching does, and how it relates to the preempt / cancel-intermediate / skip-intermediate settings — with the trade-offs of each so users can configure it confidently.
Reported from customer feedback on a Clari call (internal). Source: Slack thread.
Problem description
The documentation does not clearly recommend batching deployments as the pattern when many PRs/commits target a single stack in quick succession. Without this guidance, users reach for ad-hoc workarounds (e.g., manually enabling preempt / cancel-intermediate) and aren't sure they've landed on the supported best practice.
Suggestions for a fix
Add a best-practices note stating the recommendation to batch deployments for high-PR-volume stacks, what batching does, and how it relates to the preempt / cancel-intermediate / skip-intermediate settings — with the trade-offs of each so users can configure it confidently.
Reported from customer feedback on a Clari call (internal). Source: Slack thread.