-
Notifications
You must be signed in to change notification settings - Fork 2
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
change from submodule to subtree #1
Comments
So you think it's related to your rights in the org? |
No, this is propagation of authentification information to submodules, and with the recent change to PATs, this has become a bit of a pain. Cf. https://medium.com/@alexander.sirenko/using-github-access-token-with-submodules-5038b6d639e8. Subtree shouldn't have these issues as it creates a local copy that behaves like any other repo content. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Ubuntu 20.04.3, I got an authorization error when pushing from a repo checked out with
--recurse-submodules
(no changes in the submodules). It works seamlessly, when checking out without submodules and then applying, committing and pushing the same changes. While it is not clear why this is happening, this calls for a shift fromsubmodule
tosubtree
.The text was updated successfully, but these errors were encountered: