Client pulling submodules with orig credentials
See original GitHub issueDescribe the bug
Client pulling submodules with orig credentials, resulting with failure.
Version & OS
macOS @ 2.4.0
Steps to reproduce the behavior
git clone
forked repo with 3rd pty submodule
Expected behavior
The client issuing an attempt to clone submodule with orig
credentials instead of user/config declared.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Jenkins: Retrieving submodules with Git - Stack Overflow
In September 2016, Jenkins is planning to release a new feature that will allow submodules to share the credentials of the parent repository....
Read more >Authentication failed cloning public repo containing submodules
Description When cloning my repo using HTTPS containing two submodules, I receive the following: ... Client pulling submodules with orig credentials #9456.
Read more >Git - Submodules - Git SCM
Pulling in Upstream Changes from the Submodule Remote ... The simplest model of using submodules in a project would be if you were...
Read more >Stored git credentials not used when submodule is updated
Jacob Keller is actively developing and testing two pull requests to implement authentication for git submodules. The pull requests are git-client-plugin ...
Read more >Using Git submodules with GitLab CI/CD
When your submodule is on the same GitLab server, you should use relative URLs in your .gitmodules file. Then you can clone with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@charlesrocket could you share the log file? That may better help me understand the issue.
To access the log files go to the file menu in GitHub Desktop and select
Help
>Show Logs in Finder (macOS) or Explorer (Windows)
.The log files are created daily – please upload a log file as an attachment from a day where you experienced the issue.
@steveward obviously 😃 simplicity is a reason
desktop
got these extra miles?