Monorepo changed packages done right

  1. Git diff between 2 commits to get the files changed
  2. Compile a list of packages that are directly affected by the files changed
  3. Compile a list of packages that are indirectly affected by the packages directly affected
  • feature-branch-1 starts off from branching on ref 1 and is only merged after feature-branch-2 (no specific reason)
  • feature-branch-1 only touches package-b, so the changed packages for this should be package-{a,b}
  • feature-branch-2 touches package f, which means changed packages for this one should be package-{a,d,f}
  • feature-branch-1 -> ref1
  • feature-branch-2 -> ref2

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Springboot App monitoring with Grafana & Prometheus

Inside The Inner Hexagon: Component Tests

Microsoft Teams Apk Download

Microsoft Teams Apk Download

Learning C++: Using Arrays

Tutorial Fuzzy Logic Mamdani for Arduino

Tutorial Fuzzy Logic Mamdani for Arduino

Tips To Keep In Mind While Developing a Mobile App

Setting up Django with Nginx, Gunicorn and AWS ECS

Object-Oriented Design Concepts in 5 mins

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
Flavio Carvalho

Flavio Carvalho

More from Medium

Release 0.3 Code Reviews

Solving for developer productivity with code generation

The Naive View of a Rookie

All the tech

GraphQL Proof of Concept in Mercadona