Skip to content

Conversation

vfdev-5
Copy link
Collaborator

@vfdev-5 vfdev-5 commented May 30, 2022

New version of git checks folder owner and errors with 'fatal: unsafe repository' if owner is different.
Thus, root_dir="$(git rev-parse --show-toplevel)" is failing.

To fix the issue, just added all folders as safe directories

New version of git checks folder owner and errors with 'fatal: unsafe repository' if owner is different.
Thus, `root_dir="$(git rev-parse --show-toplevel)"` is failing.

To fix the issue, just added all floder as safe directories
git rev-parse --show-toplevel
Copy link
Contributor

@datumbox datumbox left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@datumbox datumbox merged commit 03eda6e into pytorch:main May 30, 2022
YosuaMichael pushed a commit to YosuaMichael/vision that referenced this pull request May 30, 2022
New version of git checks folder owner and errors with 'fatal: unsafe repository' if owner is different.
Thus, `root_dir="$(git rev-parse --show-toplevel)"` is failing.

To fix the issue, just added all floder as safe directories
git rev-parse --show-toplevel
YosuaMichael added a commit that referenced this pull request May 30, 2022
New version of git checks folder owner and errors with 'fatal: unsafe repository' if owner is different.
Thus, `root_dir="$(git rev-parse --show-toplevel)"` is failing.

To fix the issue, just added all floder as safe directories
git rev-parse --show-toplevel

Co-authored-by: vfdev <vfdev.5@gmail.com>
facebook-github-bot pushed a commit that referenced this pull request Jun 1, 2022
Summary:
New version of git checks folder owner and errors with 'fatal: unsafe repository' if owner is different.
Thus, `root_dir="$(git rev-parse --show-toplevel)"` is failing.

To fix the issue, just added all floder as safe directories
git rev-parse --show-toplevel

Reviewed By: NicolasHug

Differential Revision: D36760912

fbshipit-source-id: f2220269833e0cf25beafa71dba84709fe0113e2
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.

3 participants