Closed Mte90 closed 2 years ago
Thanks for opening this pull request! Make sure CHANGELOG.md
gets updated with this change, additionally any docs that need updated can be found at https://github.com/Varying-Vagrant-Vagrants/varyingvagrantvagrants.org
GitHubThe VVV docs and website. Contribute to Varying-Vagrant-Vagrants/varyingvagrantvagrants.org development by creating an account on GitHub.
we would need this in the site provisioner too, it'll probably impact some utilities provisioners as well, is it not possible to run the command with the necessary user and ownership to avoid needing this?
we would need this in the site provisioner too, it'll probably impact some utilities provisioners as well, is it not possible to run the command with the necessary user and ownership to avoid needing this?
I want to see what happen in the CI before to do other changes.
So with safe works let's see with noroot
.
So seems that this PR fix that issue.
so other provisioners already do this and aren't affected, at least in the main VVV git repo
I see that error, working on a fix:
default: fatal: unsafe repository ('/home/vagrant/.nvm' is owned by someone else)
default: To add an exception for this directory, call:
default:
default: git config --global --add safe.directory /home/vagrant/.nvm
default: fatal: unsafe repository ('/home/vagrant/.nvm' is owned by someone else)
default: To add an exception for this directory, call:
default:
default: git config --global --add safe.directory /home/vagrant/.nvm
Ref: https://github.com/Varying-Vagrant-Vagrants/VVV/issues/2593
So this is a test that is adding the repository in the safe list without fixing the permission itself
Checks
develop
branch not thestable
branch.