Context
We are currently following a mono repo approach for our Solana programs in which all programs reside on the same repo. This was clearly a convenient approach on the initial project states.
We are now starting to think about CI configurations for publishing packages at #148 and #147 . Having everything on the same git repository might force us to generate path dependent complex CI configurations.
Goal of discussion
Shall we break the monorepo, having a dedicated git repo for each solana program ?