enable non-local git server integration

[paulkaefer]

As per this thread, users or organizations housing code and git repositories on a remote server cannot integrate their revision control into EG.

While accessing git via the command-line works well and gives you more power, it would be nice to see committing and viewing commit history built-in to EG.

[CaseySmith]

@paulkaefer, you are correct too...  the Git integration does not work with programs opened in EG through a SAS server (ex. SASApp->Files or even Local->Files in the Servers view or file open dialog), because there are currently no APIs in the SAS server that support.  For the Git integration in EG to work, EG has to have file system access (either local or via UNC path) to the user's "working" Git repo (the repo in which a user works).  In other words, the program has to be opened from a Git repo that is accessed via the local file system or a UNC path into EG.

So, here is the recommended way (which follows the Git model) to store your SAS programs on a server *and* be able to use the Git integration in EG...

1. Store your programs in a "central" Git repo on a server somewhere.  (This is your remote/origin/central repo -- from which all users clone/pull and to which all users push/merge.  It does not have to be on the same machine as a SAS server, but can be.)
2. Each user clones the central Git repo from your server to their respective local machines (a location accessible via their local file system or a UNC path).  (This is each users' local working repo.)
3. Users open SAS programs from their respective local working repo (again, via local file system or UNC path) into EG.
4. Users edit the programs and commit changes to them using EG, which updates their respective local/working Git repo.  (They can also view Git history, diff, etc.)
5. When ready to make their commits official/production/available to "the rest of the world" (other users), users push their local repo changes (in a branch) (using a Git GUI or Git command-line outside of EG) back to the central/remote/origin repo.