In it's current form, this tool causes negative impact if run as a user that has privileges - it winds up changing the ownership of .git/index in repos if you cd into another account.
It can be mitigated by removing/disabling the 'dirty repo' support by removing the call to 'find_git_dirty' in prompt.sh PROMPT_COMMAND.
I do not know yet of any way to keep git status from modifying that file. Opened a stackoverflow question on the topic, will see if anyone has a suggestion:
In it's current form, this tool causes negative impact if run as a user that has privileges - it winds up changing the ownership of .git/index in repos if you cd into another account.
It can be mitigated by removing/disabling the 'dirty repo' support by removing the call to 'find_git_dirty' in prompt.sh PROMPT_COMMAND.
I do not know yet of any way to keep git status from modifying that file. Opened a stackoverflow question on the topic, will see if anyone has a suggestion:
https://stackoverflow.com/questions/47436939/how-to-run-git-status-without-modifying-git-index-such-as-in-a-prompt-command