$HOME/.gitconfig is your global config for git. There are three levels of config files. cat $(git rev-parse –show-toplevel)/.git/config (mentioned by bereal) is your local config, local to the repo you have cloned. you can also type from within your repo: git remote -v And see if there is any remote named ‘origin’ listed in it. … Read more
I had the same problem, I followed this post and others of the same kind without success :-(( Finally, I found the solution: I had to add my new rsa identity in my machine! So, first of all I created a new rsa key: ssh-keygen -t rsa -C “giordano.scalzo[at]gmail.com” -f ~/.ssh/id_rsa_heroku then added it to … Read more
Restart your ssh agent! killall ssh-agent; eval `ssh-agent`
The difference is that with simple, git push (without passing a refspec) will fail if the current branch isn’t tracking a remote upstream branch (even if a branch with the same name exists on the remote): $ git checkout -b foo Switched to a new branch ‘foo’ $ git config push.default simple $ git push … Read more
You can use git filter-branch –index-filter ‘git rm -r –cached –ignore-unmatch <file/dir>’ HEAD This will delete everything in the history of that file. The problem is that the file is present in the history. This command changes the hashes of your commits which can be a real problem, especially on shared repositories. It should not … Read more
The answer is there, git is telling you to fetch first. Probably somebody else has pushed to master already, and your commit is behind. Therefore you have to fetch, merge the changeset, and then you’ll be able to push again. If you don’t (or even worse, if you force it by using the –force option), … Read more
If this is your first push, then you might not care about the history on the remote. You could then do a “force push” to skip checks that git does to prevent you from overwriting any existing, or differing, work on remote. Use with extreme care! just change the git push **-u** origin master change … Read more
I’ve found this one: git push rorg ‘refs/remotes/korg/*:refs/heads/*’ And it pushed all my remote branches from korg to rorg (even without local copies of the branches). See the output below: Counting objects: 293, done. Delta compression using up to 4 threads. Compressing objects: 100% (67/67), done. Writing objects: 100% (176/176), 48.32 KiB, done. Total 176 … Read more
HEAD points to the top of the current branch. git can obtain the branch name from that. So it’s the same as: git push origin CURRENT_BRANCH_NAME but you don’t have to remember/type the current branch name. Also it prevents you from pushing to the wrong remote branch by accident. If you want to push a … Read more
Best Option Probably the cleanest, least confusing, and safest way to push into your non-bare remote repository, is to push to dedicated branches in the remote that represent your laptop branches. Let’s look at the simplest case, and assume you have just one branch in each repo: master. When you push to the remote repo … Read more