I'm looking for best practices of working with multiple site collections with SPGo. Let's have an application (SharePoint related) that you would try on the Staging environment first. For that reason, I'm forced to create a copy of solution files under a different folder (VS Code - workspace) and configure spgo.json with appropriate values. Now... if I introduce any change to the app I must overwrite the corresponding file in the "prod" version with the one that I changed in the "staging" version or I am missing something?
Is there any better practice to address the above problem? Is there any configuration setting that will allow me to choose which environment I want to push the code while publishing workspace?
I'm looking for best practices of working with multiple site collections with SPGo. Let's have an application (SharePoint related) that you would try on the Staging environment first. For that reason, I'm forced to create a copy of solution files under a different folder (VS Code - workspace) and configure spgo.json with appropriate values. Now... if I introduce any change to the app I must overwrite the corresponding file in the "prod" version with the one that I changed in the "staging" version or I am missing something?
Is there any better practice to address the above problem? Is there any configuration setting that will allow me to choose which environment I want to push the code while publishing workspace?