1. Refreshing Remote Repositories Failed Sourcetree Test
2. Refreshing Remote Repositories Failed Sourcetree File
3. Refreshing Remote Repositories Failed Sourcetree System

Feb 26, 2016 Click on the 'Clone/New' button. Click on 'Clone Repository'. Fill in the remote repository URL (Both HTTPS and SSH will work) and all other details. If you're using HTTPS in SourceTree for the first time, SourceTree might prompt you with an authentication window to access your Bitbucket account. Jul 13, 2017 In Sourcetree, check the left pane for Remotes Right click on it and select New Remote Insert the link to your repo and click on OK Once that's done, just do a Pull from your branch and commit your changes to the repo. SourceTree 'fatal: Authentication failed for', Mac OSX El Capitan. I cloned some remote repos a few couple of weeks ago, and have been pulling my team's updates in SourceTree. Mac OSX El Capitan. I cloned some remote repos a few couple of weeks ago, and have been pulling my team's updates in SourceTree with no issue.

I use

Feb 01, 2012 Using submodules and subrepositories. By Steve on February 1, 2012. A headline feature of SourceTree 1.3 is the support for submodules (in Git) and subrepositories (in Mercurial). The terms may be different, but they refer to the same concept; that of nesting other repositories within the folder structure of your own repository.

SourceTree to manage all my Git repositories, it's a great tool but sometimes something goes wrong with remote tags refs in one of my work repositories and I get error messages when I do a push that tells me that a bunch of tags have been rejected. Now I never actually create any tags so this is a little confusing. Cloning a fresh version of the repository fixes this but is not a solution all the time, especially if you have a bunch of stashes. Luckily there is an option in SourceTree to disable pushing tags to remotes.
This is the kind of error message I get...
Git
The culprit is shown below. In the 'push' dialog there is an option to 'Push all tags'. Unticking that makes the errors go away.

There is a better way to do this via Preferences under the 'Git' tab simply untick 'Push all tags to remotes' and you're done.

-i

Hello,

I am having an error when I try to push my changes to a remote repository.

This is a sumarry of what I did:

1- On the remote server, create the repository using 'git init /root/my_project'

2 - On the remote server, I added the files with 'git add file.txt'

3 - On the remote server, I've commited my changes with 'git commit -a -m 'description of commit'

4 - On my machine, I've used git clone ssh://root@192.168.1.2:22/root/my_project/

5 - Then on my machine, I make some changes to files and commit them using the same commands as on the remote server.

6 - Then, after the commit, I try to use the command 'git push' with defaults to my origin and the master branch but I always get the same error message:

root@192.168.1.2r's password:Counting objects: 5, done.Delta compression using up to 2 threads.Compressing objects: 100% (3/3), done.Writing objects: 100% (3/3), 317 bytes | 0 bytes/s, done.Total 3 (delta 2), reused 0 (delta 0)remote: error: refusing to update checked out branch: refs/heads/masterremote: error: By default, updating the current branch in a non-bare repositoryremote: error: is denied, because it will make the index and work tree inconsistentremote: error: with what you pushed, and will require 'git reset --hard' to matchremote: error: the work tree to HEAD.remote: error:remote: error: You can set 'receive.denyCurrentBranch' configuration variable to

remote: error: 'ignore' or 'warn' in the remote repository to allow pushing into

remote: error: its current branch; however, this is not recommended unless youremote: error: arranged to update its work tree to match what you pushed in some

remote: error: other way.remote: error:remote: error: To squelch this message and still keep the default behaviour, set

remote: error: 'receive.denyCurrentBranch' configuration variable to 'refuse'.To ssh://root@192.168.1.2:22/root/my_project/ ! [remote rejected] master -> master (branch is currently checked out)error: failed to push some refs to 'ssh://root@192.168.1.2:22/root/my_project/'

Can you guys help me with this? I don't know where I am wrong.

Your remote server has to be 'bare' and it doesn't look like yours was...

Hence the error message 'By default, updating the current branch in a non-bare repository remote: error: is denied...'

Your command should've been something like this:

~ $ git init --bare my_project.git

I hope that helps

Refreshing Remote Repositories Failed Sourcetree Test

Best Regards

Refreshing Remote Repositories Failed Sourcetree File

AJ

Refreshing Remote Repositories Failed Sourcetree System

Posting to the forum is only allowed for members with active accounts.
Please sign in or sign up to post.