![]() If it works now, consider to permanently disable the AutoRun script or enable Git’s credential manager.Otherwise, temporarily rename the AutoRun script to AutoRun~ and see whether authentication works now.If not configured, continue with the next step.Open the Windows registry and check whether for key HKEY_CURRENT_USER\Software\Microsoft\Command Processor the value AutoRun is configured. continue with step “Check Firewalls/Antivirus tools”.Ĭommand Processor AutoRun scripts may interfere with SmartGit’s authentication hook.if you are on Windows, continue with the next step.If you are not connected to a hosting provider.If your repository is connected to GitHub, check whether this problem might be related to organization access.If the command does not work without the hosting provider configured, continue below.if it stops working again, continue with step “Contact Support”.If the command works there, re-setup the hosting provider in the Preferences again and retry.If your repository is connected to GitHub, Bitbucket or another hosting provider, known to SmartGit, open the Preferences, select section Hosting Provider and get rid of the corresponding hosting provider there.SmartGit’s Hosting Provider configuration may interfere with the authentication. continue with step “Check Environment Differences”.if you are on Windows, continue with step “Check Git Credential Manager”. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |