In our repository we always want to deploy full application stacks. A stack usually consists of multiple APIs and one frontend. The repository contains multiple stacks.
Sometimes a commit contains changes to multiple components and affects multiple stacks. In these cases I want to manually decide which stacks should get deployed. For this I want to ask monobuild for a list of stacks, which changed in this commit.
We should be able to identify stacks in the graph because they don't have any incoming dependencies.
In our repository we always want to deploy full application stacks. A stack usually consists of multiple APIs and one frontend. The repository contains multiple stacks.
Sometimes a commit contains changes to multiple components and affects multiple stacks. In these cases I want to manually decide which stacks should get deployed. For this I want to ask monobuild for a list of stacks, which changed in this commit.
We should be able to identify stacks in the graph because they don't have any incoming dependencies.
Example:
Given these components
lib2
changed in the last commitRunning
monobuild diff --only-components-without-incoming-dependencies
could output: