How to Resolve Heroku's 'not authorized to access newname' Git error. When you see the 'not authorized to access newname' error, it probably. means that your Git configuration is incorrect. For example, my .git/config file had the following:

[core]
 repositoryformatversion = 0
 filemode = true
 bare = false
 logallrefupdates = true
[remote "heroku"]
 url = git@heroku.com:newname.git
 fetch = +refs/heads/*:refs/remotes/heroku/*

Notice the highlighted words. Just change newname to the actual project name and you should be fixed.

Scripting the Heroku Push

This tip falls under the KISS principle. I recently started using the Heroku service to run some Rails websites. After making changes and committing them to your local Git repository, those changes are pushed to Heroku using the command git push heroku master. Since I'm likely to forget and since it's four words I created a file called script/push with that command. Here are the steps.

1. Create a file called script/push with one line: git push heroku master.
2. Run chmod +x script/push
3. Run git add script/push.
4. Run git commit -m "scripting the Heroku push".
5. Run script/push.

That's it. Just script/push whenever you need to deploy.