Repository navigation
Help with Git Permissions for Multiple Users Accessing UiPath Process on Shared Folder #5547
Unanswered
PabloGodoyCalderon
asked this question in
Q&A
Replies: 1 comment
|
That error is about repository ownership. If UiPath is calling native Git and the folder is controlled by users you trust, each affected account can add that exact path to its global Git config. git config --global --add safe.directory "//server/share/path/to/repo"Use the path Git reports, and keep access to the share restricted. The entry lets Git trust the repository. Windows permissions still control who can write, and everyone using that same checkout still shares its current branch, index, and working files. If both people need to change branches or commit independently, separate working copies pointed at the same remote solve that part. If UiPath uses an embedded Git implementation, check whether it reads the user Git config before relying on this command. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi :)
I’m working with UiPath on a Virtual Machine (VM) running Windows where I can’t install Git. To work around this, I transfer my UiPath processes to my personal computer (also running Windows), upload the processes to Git repositories, and then transfer the repository folder to the VM.
Everything works fine up until this point, but the problem arises when a colleague accesses the process (saved in shared folders accessible from multiple VMs and different users) with a different user account. When they try to do something related to Git, such as pull, push, commit, etc., they get the error:
"Repository Path '...' is not owned by current user."
Is there a way to enable multiple users to pull, push, commit, etc., on the same Git repository without creating a separate copy for each user?
All reactions