cw-template installs in the project itself, but that was designed for one-contract repos.
beaker could just strip out .github and .circleci from those folders (or we use a new cw-template branch).
What would be more interesting is a top level, multi-contract test harness. cw-plus has an example for monorepos, but I am sure that can be simplified (and remove some of our optimisations for 15+ packages in parallel)
Similar to https://github.com/osmosis-labs/beaker/issues/35
cw-template installs in the project itself, but that was designed for one-contract repos.
beaker could just strip out .github and .circleci from those folders (or we use a new
cw-templatebranch).What would be more interesting is a top level, multi-contract test harness.
cw-plushas an example for monorepos, but I am sure that can be simplified (and remove some of our optimisations for 15+ packages in parallel)