When you run `heroku apps:create ...` the Heroku utility sets up a remote for you (or it should). If you don't run create from inside of your git repo, then you'll have to set up the remote as a separate step.
...at least I'm pretty sure that's the case (almost positive).
Shareabouts Developers group.
Monster:~ stevevance$ heroku apps:create shareabouts1
Creating shareabouts1... done, stack is cedar
http://shareabouts1.herokuapp.com/ | g...@heroku.com:shareabouts1.git
Monster:~ stevevance$ cd Sites
Monster:Sites stevevance$ cd shareabouts1
Monster:shareabouts1 stevevance$ ls
CHANGELOG.md ci requirements.txt
LICENSE.txt doc src
Procfile dotcloud.yml wsgi.py
Monster:shareabouts1 stevevance$ git push heroku master:master
fatal: 'heroku' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
git remote add heroku g...@heroku.com:shareaboutstest.git
Creating shareabouttest13... done, stack is cedar (I see the application was created)
Then had a failure here:
$ git push heroku master:master
fatal: Not a git repository (or any of the parent directories): .git