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 [email protected]:appname.git
More info in Heroku's manual "Deploying with Git"
Question is: How can I see latest version in Heroku repository?
6 Answers 6
The correct answer is actually so simple. You don't need to checkout anything, neither do you have to resort to COMMIT_HASH hacks (which don't work on Cedar stack). All you need to do is: git ls-remote <remote>
> git ls-remote heroku
ddaszxcewb585d3a3c00de816a197b14462791a3 HEAD
ddaszxcewb585d3a3c00de816a197b14462791a3 refs/heads/master
4 Comments
git ls-remote heroku | awk 'END{print 1ドル}' | xargs git showheroku releases:rollback. Use heroku releases to see what is in production.If you've just pushed and want to make sure you're up-to-date, then you can just run git remote show heroku and you'll see output similar to this:
* remote heroku
Fetch URL: [email protected]:XXX.git
Push URL: [email protected]:XXX.git
HEAD branch: master
Remote branch:
master tracked
Local ref configured for 'git push':
master pushes to master (up to date)
That (up to date) at the end will be replaced by (fast forwardable) if it is not up to date.
Or, if you're wanting to see the full commit log for the heroku remote, the only way I know how is to check it out first. git checkout heroku/master will give you the current commit hash and commit comment: HEAD is now at <short commit hash>... <commit comment>, and git log will give you the rest of the story.
3 Comments
You may now want heroku releases and you'll see like 5 commits. a start at least.
1 Comment
what about
git log heroku/master
1 Comment
master branch reference may or may not get updated to the SHA that was deployed.if you've run into the situation, like i just did, where a co-worker rolled back your heroku app to a release that doesn't show in heroku releases because they only keep track of 2 releases... the checkout of heroku/master method won't help, because HEAD is not what is deployed anymore.
the undocumented to the rescue:
$ heroku console "ENV['COMMIT_HASH']"
"12abcdef"
4 Comments
'heroku console' has been disabled (devcenter.heroku.com/changelog-items/109). I tried heroku run "ENV['COMMIT_HASH']" but I get bash: ENV[COMMIT_HASH]: command not found. When I use echo I get the string ENV[COMMIT_HASH].heroku run console and you can see what is inside of the ENV['COMMIT_HASH'] variable by running heroku run echo $ENV['COMMIT_HASH'] (since it is an environment variable, you need the '$' - much like echo $PATH).heroku is using plain old Git underneath, so..
show the latest 5 commits on current branch:
git log -5
show commit history via Git's gui:
gitk
view current status (it'll show if you have any uncommited files):
git status
heroku releases:rollback, then the version in production will change, but the Heroku repository will stay absolutely the same. Useheroku:releasesto see what is in production.