A post showing concrete CI time savings on a real (or realistic) Go monorepo would do more for adoption than spec documentation.
Ideas
- Run BuildGraph against a well-known open-source Go monorepo
- Show: "12 services, changed 1 shared function, BuildGraph correctly identified 2 rebuilds, saved N minutes of CI time"
- Publish on personal blog + share in Go community channels
A post showing concrete CI time savings on a real (or realistic) Go monorepo would do more for adoption than spec documentation.
Ideas