Ask HN: Monorepo (with git) best practices

Just getting started with a relatively small group who has decided to merge several small repos into one.

In this case, the code varies in purpose (some code in the current repos is reusable, some combine to make a single project and others are just stand alone stuff) and implementation (C++, Python, Java, SQL etc.) ++

I have worked with both monorepos and lots of little repos before. I personally prefer the monorepo approach but recognize both the many repo and monorepos methods are valid.

However, when I have worked successfully with a monorepos it was with a large teams and there was lots of tooling around SVC system to support it.

In this case we are small group using GIT and don’t have the resources to create a lot of tooling to support monorepos approach.

So my question is: what light weight approaches to monorepos management are recommended, what’s to be avoided. etc.

Thanks in advance!