Skip to content
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

Merged
merged 2 commits into from
Nov 18, 2024

Conversation

dblanken-yale
Copy link
Contributor

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

  • Adds instructions should users run into a safe directory issue

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.
Copy link

Visit Site

Created multidev environment pr-795 for yalesites-platform.

Copy link
Contributor

@codechefmarc codechefmarc left a 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.

@dblanken-yale
Copy link
Contributor Author

Gotcha; updated the command so it includes app. Good that I added you! haha

Copy link
Contributor

@codechefmarc codechefmarc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good to go!

@dblanken-yale dblanken-yale merged commit 00f131c into develop Nov 18, 2024
3 checks passed
@dblanken-yale dblanken-yale deleted the git-safe-directory branch November 18, 2024 19:13
@yalesites yalesites mentioned this pull request Nov 20, 2024
@yalesites
Copy link

🎉 This PR is included in version 1.11.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants