Hey everyone, I am implementing version control with git-source-control on our codebase and I ran into a pretty strange issue. I believe I have the set up (mostly) correct as the behavior with .cls files is exactly as expected. However, I noticed that git is not keeping track of any changes to CSP files.

Specifically, if a new CSP file is created and saved, I will get the following output:

exporting new version of /csp/testdb/wrc.csp to C:\InterSystems\IRIS\mgr\repo\TESTDB\csp\testdb\wrc.csp

Added /csp/testdb/wrc.csp to source control.

C:\InterSystems\IRIS\mgr\repo\TESTDB\csp\testdb\wrc.csp removed from uncommitted list

exporting new version of /csp/testdb/wrc.csp to C:\InterSystems\IRIS\mgr\repo\TESTDB\csp\testdb\wrc.csp

Added /csp/testdb/wrc.csp to source control.

C:\InterSystems\IRIS\mgr\repo\TESTDB\csp\testdb\wrc.csp removed from uncommitted list

However, if I change a CSP file and save it, it simply compiles with no exporting, and git is unaware of any changes. I can neither see the change when running git status nor git add the file. When I went digging in the git repository location, the csp file is indeed completely unchanged (but the CSP files stored in /csp/ have changed). This is different to the behavior I observe when making changes to a .cls file. When I change a .cls file and save those changes, the output is as follows:

exporting new version of PET.DataFile.CLS to C:\InterSystems\IRIS\mgr\repo\PETDB\cls\PET\DataFile.cls

and git becomes aware of the change. 

Has anyone else seen this problem before? Did I neglect to turn on a setting somewhere? I have a sneaking suspicion that this might have something to do with server vs client side editing, but I did follow the official documentation around defining workspaces and I also made sure that there wasn't conflicting local folder settings. Any ideas would be much appreciated. Thanks!