git-remote

I am deploying an app on Heroku so I created a Heroku app from a repo and then did git push heroku master . When I do this it keeps giving me the error: ! Your key with fingerprint xxx is not authorized to access heroku-app. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. I tried various things with changing my SSH keys including deleting them all and creating new ones. Still it gives me the same error. I have added the key to Heroku. Then I tried running ssh -vT git@heroku.com:heroku-app.git and the result was:

I'm using Git to version a series of binary files. They compress pretty well, but my central repos do not seem to be compressing when I push to them. They're eating up a decent amount of my quota, so I was looking to see if there was a way to force the remote repo to do a GC. Is this possible? I'm working on Project Locker so I don't believe I have SSH access to go in and GC the repo myself. Any ideas? Thanks. If you can't run git gc yourself, you're going to have to trick it into running automatically. You won't have quite such full control over it then, but you should at least be able to get

For deploying to Heroku, I use git push heroku master . But how do I see which revision I pushed up to heroku? (I'm often in doubt if I pushed the recent version up) For those not familiar with it, Heroku's create script generates a remote git repository that you push to. Upon push, the code is deployed magically. Heroku adds a remote repository to the local one in the form: $ git remote add heroku git@heroku.com:appname.git More info in Heroku's manual "Deploying with Git" Question is: How can I see latest version in Heroku repository? If you've just pushed and want to make sure you're up-to

From the man page: Deletes all stale tracking branches under <name>. These stale branches have already been removed from the remote repository referenced by <name>, but are still locally available in "remotes/<name>". So I removed a bunch of branches using git push origin :staleStuff and then ran git remote prune origin However, only one single local branch was pruned. Some of these branches were created by me, some by co-workers. Does this indicate that I wasn't tracking those branches correctly in the first place? When you use git push origin :staleStuff , it automatically removes origin

I have the following remotes set up: $ git remote korg rorg And the following branches: $ git branch -a * (no branch) remotes/korg/gingerbread remotes/korg/gingerbread-release remotes/korg/honeycomb remotes/korg/honeycomb-mr1-release remotes/korg/master remotes/m/android-2.3.3_r1 -> refs/tags/android-2.3.3_r1a remotes/m/gingerbread -> korg/gingerbread Now I wish to push all the remote branches from korg to the rorg remote. How do I do that? Preferably without making a local branch for each first, if that is avoidable. A quick test making some temporary repositories shows you can construct a

I'm the only one in my organization who's making commits with the following message: Merge remote-tracking branch 'origin/develop' into develop Not sure what I'm doing to cause them, but I'd like to stop. What command am I issuing to create this commit, and what is the proper command I ought to be using to not produce it? Richard Hansen git pull is probably creating the commit. If you make a local commit and then run git pull after someone else pushes a commit up to the repository, Git downloads the other developer's commit and then merges it into your local branch. How to avoid these merge