![]() The easiest method is -> Type "cred" -> Click on "Credential Manager" tile. Perhaps your credentials are bad, and for some reason the GCM cannot purge them - a manual pruge might be helpful. If that's the case, then we need to determine why that is. Given that I do not see any GCM tracing in the git.txt file, either git-credential-manager.exe isn't being launched or it is failing to trace. User.name=Wesley are you actually seeing a dialog asking for credentials? What you should be seeing is a windows containing a web browser control displaying the Azure Authentication Portal (looks something like the image below). Http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crtį=git-lfs filter-process Looks like it created the Widows Credentials this time.Įrror: cannot spawn askpass: No such file or directoryĮrror encountered while cloning the remote repository: Git failed with a fatal error.įatal: could not read Username for ' terminal prompts disabled Open a Command Prompt with the same privileges as used to enable the tracing.īecause environment variables are inherited at process start up, any process (console, Visual Studio, other Git tools) which are running will continue logging until Here is the log.Given that the log file can get large quickly, disabling logging is something you'll want to do at some point. Please redact any sensitive or personally identifiable information from the log before sharing it publicly. Attach the file found at "%UserProfile%\git.log" to this issue.Run setx GCM_TRACE %UserPorfile%\git.log.Run setx GIT_TRACE %UserProfile%\git.log.Open a Command Prompt with the same privileges as you would give Visual Studio (same user, elevated if VS is elevated, otherwise non-elevated).But you should fix this issue in the new this sounds rather broken.Ĭan you enable some logging so that we can better see what is happening? Git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=manager-st submodule update -init -recursiveīut the same issue appears when I enter 'git pull' in Git Bash - it appears to me that the token is not saved on my machine. Git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=manager-st pull origin feature/preferences Git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=manager-st fetch origin My usal flow is like that - SourceTree version 2.1.2.5: But for some reason this does not change my credentials on a computer. I am getting prompted for my Windows Live credentials - and I successfully enter everything. I've checked windows credential store - there is no entry for my repository. ![]() Later I am able to enter my credentials and the repo is checked out. Logon failed, use ctrl+c to cancel basic credential prompt. I am able to pull everything but every time I pull I have to enter credentials - this fails with very not-informative: This is something our team is actively looking into now.I have an odd issue with my git setup for VS Team Foundation. That way, users not using checkout and users using container actions can take advantage of that solution. ![]() This is better solved at an actions ecosystem level, rather than solving it in the checkout action. It only really addresses this issue for checkout users, but this is more of an actions ecosystem problem.Overwriting the git global config and not persisting any changes back to the original global config may break some user expectations on self hosted runners.If you run checkout on the root machine, and you have a container action with git commands, you are still going to fail unless you set the config in that container, which checkout can't do for another step.We could try to persist this temporary global configuration we set in checkout for the duration of your job, but there are few problems with that: Why don't we persist the configuration we use in actions/checkout ![]() While any folders created may be owned by the container user. When the runner maps the working directory mounts into your job container or step container they are owned by the runner user, not the container user, causing this issue. Why is the parent directory owned by a different user? If you are failing inside a container action, you will need to run this inside your container action script. Git config -global -add safe.directory "%(prefix)/$GITHUB_WORKSPACE"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |