Putting SCOPE directory under version control
Posted: Sat Dec 02, 2017 12:00 pm
I thought the fresh installation of SCOPE 7 is a good opportunity to put the SCOPE folder under version control using git.
With that, it'll be possible to track what files are changed by installers for example and to go back to a previous state of the SCOPE folder if something goes wrong.
I guess it will also come in handy if I screw up a preset file and have to revert it. Or a Modular patch. Or a project file...
Here I was using just the command line tool to add the proTone files to the git repository after putting them into place:
(There are also GUI tools that integrate with the Windows Explorer (like TortoiseGit for example) and make it easier for people who are not familiar with the command line).
Here's the log after doing the initial installation, importing my key file and adding Six String as well as proTone:
Now I could easily go back to the state of the fresh installation by checking out the corresponding commit and start again from that point for example.
I guess this could be nice when you demo a device and then want to get rid of the installed files if you don't like it or don't really need it.
To not mess up your installation in the first place, you could create a new branch and install the demo on that branch. Now to get rid of the demo you just need to checkout (switch to) the master branch again and delete the demo branch.
With that, it'll be possible to track what files are changed by installers for example and to go back to a previous state of the SCOPE folder if something goes wrong.
I guess it will also come in handy if I screw up a preset file and have to revert it. Or a Modular patch. Or a project file...
Here I was using just the command line tool to add the proTone files to the git repository after putting them into place:
(There are also GUI tools that integrate with the Windows Explorer (like TortoiseGit for example) and make it easier for people who are not familiar with the command line).
Here's the log after doing the initial installation, importing my key file and adding Six String as well as proTone:
Now I could easily go back to the state of the fresh installation by checking out the corresponding commit and start again from that point for example.
I guess this could be nice when you demo a device and then want to get rid of the installed files if you don't like it or don't really need it.
To not mess up your installation in the first place, you could create a new branch and install the demo on that branch. Now to get rid of the demo you just need to checkout (switch to) the master branch again and delete the demo branch.