@AndrewHowell, we use version control for SAS code, and it works great. You can certainly develop a workflow for not just committing development changes at the end of the day, but also using branching and tagging in git for production-ready/tested versions. A production environment can pull approved versions from the repository.
I've done enough testing of versioning .spk files to know that, while it's not ideal (.spk are binary files, essentially a form of .zip files), it works at least to preserve versions & cover yourself in the case something corrupts or a change is made that needs to be backed out. Not sure as far as promoting an entire DI Studio process to a separate environment, but at least you can export and commit.
I do discuss version control for SAS programmers in my MWSUG 2017 paper, an update of which will be at SGF. If you're there, I would enjoy the chance to discuss further.
... View more