A change to Sourcetree would be even better! Thanks. We don't want to push everyone to use the same client, but it would be a solution to this issue.Īny suggestions that might help us work around this issue would be great. I have a feeling that if the problem as originally described was fixed, this would also work.įWIW, another git client works well in this scenario if we remove the username from the URL, but fails with the username included. It seems that they can override that default, entering valid Bitbucket credentials, but the pull/push still fails. It will prompt others for a username/password, defaulting the username to the one embedded in the URL. Sourcetree makes that difficult, allowing only the person whose Bitbucket username is embedded in the URL to do so. GitHub and set them as active: Fetch the latest version of the emsdk (not. It is really convenient for any member of the team to be able make changes to the shared working copy, then push them to Bitbucket. Specifically, we have some projects which rarely get worked on (never more than one person at a time - the binary files can't be merged) which have working copies stored on a shared networked drive (we don't have separate working copies for each team member). It has implications that affect how my team works. git config -global user.name 'your name git config -global user.email. In addition: git config -global pression 0 git clone -depth 1 cd to your newly created directory git fetch -unshallow git pull -all.I think the above info is enough to deal with the essence of the issue. Execute the following in the command line before executing the Git command: set GITTRACEPACKET1 set GITTRACE1 set GITCURLVERBOSE1. ![]() I would like it if the username in the URL was optional, and the username I enter when prompted was used to log into Bitbucket. After I delete the contents of the map I cloned my repository to Sourcetree works again. What seems broken to me is that if it is omitted from the URL, Sourcetree prompts for the username but apparently doesn't use it, as I can't log in even if I use the same username at the prompt. Url = can see how embedding the username in the URL might be a reasonable way of specifying the default. Another git client is able to pull and push from Bitbucket on the same working copies.Ĭomparing working copies which do and don't work with Sourcetree led us to discovering that Sourcetree seems to require that the username (followed by be embedded in the remote URL, something like: Enter the Github username (not the e-mail) and use your token as the password. Then go to Tools->Settings->Authentication and add a new Basic Github authentication. It will pop up a dialog to enter a username and password (which work at ), but it seemingly doesn't pass them along to Bitbucket. To prevent this after removing the old git credentials, delete Atlassian folder from all the appdata folders. ![]() Sourcetree seems to have trouble pulling and pushing from Bitbucket ( remote: Login failed due to incorrect login credentials or method) on a number of working working copies with various origins.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |