@PGriffith I actually saw that, good to know but not quite the issue I'm having. It's not any permsisions errors between copies of the repo, it's just the repo is not writable by users (as it inherits permissions from 'Program Files') so I have to run git commands as administrator (bad practice) or change the projects to user writeable (which may require stopping the gateway or have unintended side effects). I guess my question is "how are other people dealing with this?" and "how have others incorporated git into their workflow?"
Right now, we have Git invoking through the Project Update script, but we are soon looking to change that approach to a Git repo per project
That's an interesting approach. It seems like you'd lose a lot of the benefits of git... but that sounds super useful if you have developers you don't want to give ssh/rdp access to. I do repo per project; almost did git submodule but there's just too many ways someone could inadvertently overwrite your stuff
UI that triggers sendMessage commands to the GW to execute git commits
All this to get around permissions or...?
Why do you want to change Unix file rights in Windows?
I don't, I just want them to be user writable. Saying u+w
was (poor given the context) shorthand
If git have issue, it’s probably with writing to .git folder, which you can give access from within Windows once, and it should not change back
That would work as long as you were only making changes locally and not pulling changes from anywhere else. As soon as git tries to change a file it's going to croak
Windows files when created usually inherit it’s parent rights, so changing projects folder manually will fix the issue
That was my first instinct but that update failed... presumably because Windows can't handle doing anything with open files . So I'm guessing I have to stop the gateway to update permissions and I figured I'd better ask around before taking the gateway down. And if I have to take the gateway down to update permissions every time I create a new project it sounds like running git as administrator is what I'll end up doing
Running git on Windows with services makes my head hurt
Yes exactly