Run the workflow, close it, open it again - all good until now, no issue here.
Push the project to Github (I haven’t tried with other version control).
Clone the project from Github, open it, and you’ll get the pop-up below (where you press Yes). However, the auto-import does not fix it, and the globals remain undefined (see 2nd screenshot below).
At this point you can manually define the globals again, but as soon as you push the code and clone it, the same issue will occur.
The same issue occurs also with the projects that were converted from Windows-Legacy to Windows and then pushed to a repository. However, in this case it’s more severe, as you won’t even be able to manually create the globals again since another error occurs when you try to do so, and prevents you from creating any variable through the Data Manager.
The Studio version used is the latest community build received.
Hello @alexandru thank you for your answer! While we did not ignore the .project folder in our .gitignore file, we did ignore .json files in general with a few exceptions and globalVariables.json was being left behind. I’ve added it as an exception now and the issue is gone.
Since on Windows-Legacy we could get away with ignoring all settings folders,
are there any files besides globalVariables.json that are mandatory in Windows projects (from the highlighted folders)?
PS: To answer your 2nd question, the pushing/cloning was done with Git Bash.