Repo strategy in InterSystems IRIS: one repo per namespace, or one repo with multiple project folders?
My team is trying to decide on the best Git strategy for a group of related but separate projects/environments.
One side prefers one repo per project/environment/namespace for cleaner separation. The other side prefers one repo with multiple project folders so shared code and releases are easier to manage in one place.
The challenge is that these projects are separate enough that boundaries matter but related enough that some utilities and common logic may need to be reused. We also want the setup to be easy for developers to understand and not become a deployment nightmare later.
The main things we care about are:
- Maintainability
- Clear deployment/release management
- Handling shared code cleanly
- Reducing confusion for developers
- Avoiding future headaches as the number of environments/projects grows
So, I’d love to hear from people who have gone through this before:
When does separate repo per project make the most sense?
When does a single repo make more sense?
How do you handle shared code in each model?
Which approach tends to be easier for release management and long-term maintenance?
I’m not looking for a one-size-fits-all answer, just trying to understand what usually drives the right decision.