Git Repos in Multistage environment

Hi all.

I’d like to ask if it’s suggested to have one Git Repo or Multiple Git Repos for a use case where there are multiple models/connections (there are dev / test / prod databases).

Particularly I’m trying to understand how it would be possible to have a single Git Repo in a multi-instance environment (Dev, Staging, Prod) when the 3 different instances need to have different models and connections. Do we need to have the model files committed to the single Git Repo or is there a smarter way to manage that? Ideally would like to avoid exposing the Production models to Staging and Dev.

Thanks in advance.

PS. I have read a number of articles for multi-instance/multi-stage environments and in one of them there was a mention about utilising the Advanced Deployment Mode with only one Git Repo needed but I couldn’t figure out how this particular problem could be solved.

0 0 133