-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(git): document about making atomic a safe directory #795
Conversation
In some cases, vendors were receiving strange errors related to the atomic directory already existing. It turned out the real issue was that git detected strange ownership of it, and would disallow it from being brought down. While the first fix is to ensure that yalesites-org/* was marked in composer as prefer-dist in the config.json, the next is to add a safe directory to allow this to work again.
Created multidev environment pr-795 for yalesites-platform. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The command I had to run was:
git config --global --add safe.directory /app/web/themes/contrib/atomic
with the "app" specified because it was inside a container - I don't know how this would be different if not run from within Docker - i.e. a separate AMP stack - but I think changing it to that makes sense because this repo is setup to use Lando.
Gotcha; updated the command so it includes app. Good that I added you! haha |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to go!
🎉 This PR is included in version 1.11.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
docs(git): speak about making atomic a safe directory
In some cases, vendors were receiving strange errors related to the atomic directory already existing. It turned out the real issue was that git detected strange ownership of it, and would disallow it from being brought down.
While the first fix is to ensure that yalesites-org/* was marked in composer as prefer-dist in the config.json, the next is to add a safe directory to allow this to work again.
Description of work