I’ve noticed a problem when creating a bot that notifies what packages have changed on each merge request. Consider the following dependency graph:

Change package-c -> test package-{a,c}

Change package-e -> test package-{a,b,c,e}

Change package-d -> test package-{a,d}

You get the point, we only want to test the packages that are affected by a change. Getting a list of what packages changed is quite straightforward:


Imagine this, your team decides to split a monolith application into smaller packages, either in a monorepo or multi-repo, how do you promote standard scripts and ease of use when creating new packages?

Having a standard set of scripts for all the packages has its benefits:

Flavio Carvalho

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store