You can get more information with # Windows set GIT_CURL_VERBOSE=1 set GIT_TRACE_PACKET=2 # Unix export GIT_CURL_VERBOSE=1 export GIT_TRACE_PACKET=2 And then try a git push. Double-check your proxy settings if you have one. Note: git 2.8 (March 2016) adds more information on an error 35: See commit 0054045 (14 Feb 2016) by Shawn Pearce (spearce). (Merged … Read more
This worked for me, Step 1: Click on + New Repository> Clone from URL Step 2: In Source URL provide URL followed by your user name, Example: GitLab Repo URL : http://git.zaid-labs.info/zaid/iosapp.git GitLab User Name : zaid.pathan So final URL should be http://zaid.pathan@git.zaid-labs.info/zaid/iosapp.git Note: zaid.pathan@ added before git. Step 3: Enjoy cloning :).
To diagnose the problem, I ran opendiff from the Terminal. I received the following error: xcode-select: error: tool ‘opendiff’ requires Xcode, but active developer directory ‘/Library/Developer/CommandLineTools’ is a command line tools instance To solve: Open Xcode > Preferences > Locations Click on the drop-down box beside Command Line Tools and select your current Xcode version. … Read more
This method is based on history deletion: Check out the branch you made the mistake on Right click on the commit you want to reset the branch to Click “Reset current branch to this commit” Select “Hard” mode and click “OK” Unfortunately you need terminal to do this bit. Type git push origin name_of_branch –force … Read more
Might also be bad SSL cert, fix the server If you have a GIT server with an outdated or self-signed SSL cert fix the server, afterwards everything should run fine. Insecure Hotfix: Let the client accept any certificate The following solution is just a mere hotfix on client side and should be avoided as it … Read more
Based on previous answers, here is a simple sequence: Open a terminal window and cd into a folder under the repository. Then: git fsck | awk ‘{print $3}’ > tmp.txt cat tmp.txt | xargs git show > tmp2.txt Now open tmp2.txt in editor, locate your lost code, and find the commit-id on top of it. … Read more
If you are using two-factor authentication with GitHub you will need to create a personal access token and use it with SourceTree: To work with GitHub’s two-factor authentication in SourceTree you can simply use your access token instead of your password. The steps to do this are as follows: Go to your Personal Access Tokens … Read more
Check Tools > Options > Git in SourceTree, if you’re using Use Embedded Git, you can see the git version is 1.9.5 which is old, latest version of git is 2.16.2. So click Use System Git, if you install the newer version of git, after Use system Git it’ll show newer version, then try to … Read more
Select a file, whether in the ‘working copy’ display or in the ‘commit’ display, and do one of three things: option-command-B menu bar :: Actions :: Blame Selected… contextual menu :: Blame Selected… If the file you want to blame is not in the modified files list, you need to change the view to File … Read more
Unfortunately the UX path for the resolving conflicts during a rebase is quite poor in atlassian-sourcetree. After you have resolved the conflict and have all of your changes in the staging area, instead of clicking commit, go to Actions-> Continue Rebase: