Default Push Policy Options In Stack Settings

Workaround

Attach a custom push policy based on the default functionality, with the push-based trigger for proposed runs removed so only the PR diff decides.

Problem

By default, a pull request triggers a proposed run on a stack if either of two things is true: any file changed in the push falls within the stack’s project root or additional project globs, or any file in the PR’s diff against its base branch does. The push-based check looks at every file touched by every commit in the push, not just the net result of the PR. Rebasing, merging the tracked branch into the PR branch, or pushing several commits at once can pull in files unrelated to the PR’s changes, which triggers runs on stacks the PR doesn’t actually touch, and again on each new commit. Users generally expect a PR to trigger runs based on the files in its changed-files view. The default doesn’t match that, and the reason isn’t visible anywhere in the stack configuration. Users have to know how the default works internally, usually after they’ve already been surprised by unexpected runs.