What’s more, you can view existing items and new branches as well as Git flow modifications using the related option. You and your team mates can edit a specific project at the same time as the program is equipped with support for Distributed Version Control System. You can also switch between repositories by selecting the tabs at the top of the window or with a simple double click. The clean layout with straightforward options is a superior alternative to the command line, allowing you to open multiple repositories from your local or remote directories, simultaneously and view them in a list. With this program you can easily create or modify the projects you have on any of the above mentioned websites, as well as build and publish new repositories and duplicate items.īesides letting you edit your projects in a simple manner, you can also use SourceTree as a client for Mercurial and Git tools. SourceTree is an efficient desktop client that lets you connect to your online repository hosted on sites like BitBucket, GitHub and Stash. A change to Sourcetree would be even better! Thanks.A capable desktop client that lets you easily open, explore, modify GitHub projects, and publish the changes to the website 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. 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. I think the above info is enough to deal with the essence of the issue. 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. 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: Cons: - Sometimes password management becomes tricky. Easy search for the remote repos in my Bitbucket account, I can conveniently add old repos that were deleted long time ago. Repos and projects can be conveniently grouped. 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. Pros: - Very convenient tool with a nice GUI to manage GIT-repos. 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. |