If a there are two stacks that have matching prefixes, both stacks are triggered. We expect the stack that best matches the prefix should trigger a run.
We ran into this in a repo that had to root workspaces. e.g. /foo and /foo-config
Both stacks would get triggered when something changed in “foo”.
It seems the default push policy that Spacelift uses may be using startswith to find the stack. We created our own push policy to workaround this but it would be nice that the default push policy be fixed.
Log in to comment and vote
Comments1
Gold Pear
Oct 2, 2025
We ran into this in a repo that had to root workspaces. e.g. /foo and /foo-config
Both stacks would get triggered when something changed in “foo”.
It seems the default push policy that Spacelift uses may be using startswith to find the stack. We created our own push policy to workaround this but it would be nice that the default push policy be fixed.