Not claiming that there is a single “TQ recommendation” on this topic as it depends a lot on exactly what you are doing, and what technology you are using.
Being a PS team member, I also have many workspaces (E.g. one per customer/project per EDG release - I have about 30 at the moment) while that might not be true for you. So, my usage may be “unusual”.
For my projects that include software projects (e.g. with older SWP tech in them) I need everything possible so:
- When creating a new workspace for an EDG Studio install (one per project per release of EDG) I add symbolic links to the folders in my local git clone (never a whole repo in my case, as I need to 100% control what is visible to each Studio installation).
- use git Desktop app for Mac to handle branch, push, pull.
- I often browse and edit TTL using Visual Studio too, though, and that makes a difference. BBEdit sometimes too as it has a very nice diff function.
- EDG Files also works in this config
I know others who only ever edit using EDG Files function, so might have a different preferred config.
Personally, I do not directly edit anything using Files that is under git control. I always export sorted turtle and use the git diff before save or push. I like to see every detailed change before merge, but maybe that’s unusual.
FWIW there are also times when I do not use git at all and instead use an “all collections” approach. Sometimes I need two or three Studio installs running with different versions of the same graphs. If I mange them as EDG collections, then a single export zip means I can copy everything for a project to a new workspace in one easy step. This also works great when collaborating with less technical colleagues or sharing with customers who would never use git.
By export zip I mean “Zip File without system graphs”. Much better than trig IMO as it’s just a zip of TTL files.
Cheers,
David