2

We have a Git repo in C:\Program Files\Some-DB\Some-DB-Queries. When Git (or SourceTree) is run as Admin, everything works as expected. However, as non-Admin, after pulling into a local repo, Git sees those changes as uncommitted local changes.

Does Git have to be run as Admin in Windows? If not, is there a way to configure security such that Git has the proper permissions for a repo living in Program Files?

John K
  • 147
  • 2
  • 11
  • When programs write to certain areas that a normal user generally doesn't have access, UAC virtualization comes to the confusing rescue: http://blogs.windows.com/windows/archive/b/developers/archive/2009/08/04/user-account-control-data-redirection.aspx . The moral of this story is: Don't keep your data in program files. – Iron Savior Jul 01 '14 at 16:13
  • @IronSavior Thanks. Regarding Program Files, the database requires query modules to be descendants of the database application directory, so moving the files out of Program Files is not an option. – John K Jul 01 '14 at 18:40
  • That doesn't explain why your repository has to live there. – Iron Savior Jul 01 '14 at 18:44
  • @IronSavior If the working folder is still in Program Files, I don't see how that helps solve the problem with permissions. – wst Jul 01 '14 at 22:05
  • 1
    The other option would be to either change the permissions on the folder containing your repository and working directories, or to always run git using an admin account (or otherwise an account with permission). I'm not sure what you need to do in order to forsake the UAC-virtualized copy, though. – Iron Savior Jul 01 '14 at 22:53

0 Answers0