Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.
Black Breeze
•
May 27, 2025
Hi Dom! Thanks for the request.
To better understand your setup: How are you currently managing which runs should trigger for your stacks in this large monorepo? Are you using push policies, project root configuration, or some other approach to control when stacks should run?
And when commits are ignored (like in your screenshot), is this the expected behavior, or are there cases where you'd want those commits to actually trigger runs?
Orange Pond
•
May 27, 2025
We are defining the project root for the stack. Ignoring these commits is the expected behavior - this FR pertains only to disabling the notification banner for our users. This could be at the organization level for all users or at the space level for a subset of stacks.
Log in to comment and vote
Comments3
Natalia Gazda
Jul 16
Hey, thanks for the suggestion. We're archiving this one for now. It hasn't picked up much interest since it went up, so it isn't on our near-term roadmap. Archiving isn't deleting: the request stays on record, and if it gathers more votes or comments we can bring it back. If it still matters to you, add a vote or a comment so we can gauge the demand.
Black Breeze
May 27, 2025
Orange Pond
May 27, 2025
We are defining the project root for the stack. Ignoring these commits is the expected behavior - this FR pertains only to disabling the notification banner for our users. This could be at the organization level for all users or at the space level for a subset of stacks.