![]() Once you enter them, the GUI client should work fine (it uses the same username/password cache as the command line client).Īnother possible resolution is to open Windows Control Panel > User Accounts > Credential Manager > Windows Credentials, then update the password by editing the credentials for Git under the category "Generic Credentials". After selecting it, a modal would pop up, select URL and place the https link we copied from gitlab inside the URL field and select the destination folder. open GitHub Desktop from the file bar, select clone repository. ![]() It will ask for your username and password. Head over to your repository and select https and copy the link, ii. Open Git Shell, go to your repository and try any server operation (git fetch, for instance). ![]() The GitHub for Windows command line client, Git Shell, doesn't have this problem. After showing the "login required" dialog, it doesn't seem to use the new password. Unfortunately, GitHub's GUI Client for Windows doesn't seem to handle changed passwords. GitHub's client's cache git usernames/passwords. 09:17:43,533 DEBUG chet_watkins 557x1793208x2 19rp0j 10.2.164.104 "GET /admin/logging HTTP/1.1" c.a.s.i.s.CustomSecurit圜ontextPersistenceFilter Securit圜ontextHolder now cleared, as request processing completed Cause 09:17:43,455 DEBUG 557x1793210x2 k4fcng 172.27.5.113 "GET /scm/TQ/data.git/info/refs HTTP/1.1" c.a.s.i.s.CustomSecurit圜ontextPersistenceFilter Securit圜ontextHolder now cleared, as request processing completed I think a warning banner (dismissable) if the branch is tracking a remote with a different name might be useful, but it's probably not worth the effort for this niche case.09:17:40,783 DEBUG 557x1793209x2 172.27.5.113 "GET /scm/TQ/data.git/info/refs HTTP/1.1" c.a.s.i.s.CustomSecurit圜ontextPersistenceFilter Securit圜ontextHolder now cleared, as request processing completed ![]() I'm going to go ahead and close this as there's probably not much that can be done in Github Desktop to resolve the confusion. Practically, though, it seems from the command line that the tracking a different remote has little impact since doing git push my-new-branch was creating the remote branch anyway. I'd gotten used to the previous way of doing it as that's a quick and easy way to make branches from a tag (and doesn't have these issues since there's no remote branch to track). So you're right, it appears the way I created the branch leaves it tracking the other branch, and the more correct way would be to do git checkout master git checkout -b my-new-branch. It then gets more confusing because Git Desktop is showing the commits I just pushed as local commits (can undo, no 'View on Github' in history view), even though if I browse to they're there on the named branch as expected. That's confusing because the second command is what you'd normally use to push a branch created with git -b my-new-branch as well. I tried again and found that both git push origin HEAD and git push origin my-new-branch both create the branch on the remote with commits on the branch I made. The git push always creates the new branch on the remote. Seems like git being a bit strange, as I've used this technique from the command line before without having issues. Thanks for the clarification, that's good detail.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |