Why does Heroku think everything is relevant when it’s not?

Question

On Heroku, I have a production application, and I know that it has an intermediate application:

$ heroku list === My Apps testivate testivate-staging 

I have remotes for everyone:

 $ git remote -v heroku [e-mail]:testivate.git (fetch) heroku [e-mail]:testivate.git (push) staging [e-mail]:testivate-staging.git (fetch) staging [e-mail]:testivate-staging.git (push) 

A few days later, the deployment crashed my production application, so I used heroku rollback , finally created the middleware that I am currently using, and translated my code into the middleware, presumably using git push staging master . (That was a few days ago, but I'm pretty sure I did.)

Now everything works in my middleware application, so I'm trying to push my code to my production application.

However, Heroku continues to tell me that my production application has already been updated:

 $ git branch * master $ git status # On branch master nothing to commit (working directory clean) $ git add . $ git add -u $ git commit -m "trying to commit" # On branch master nothing to commit (working directory clean) $ git push heroku master Everything up-to-date $ git remote show staging * remote staging Fetch URL: [e-mail]:testivate-staging.git Push URL: [e-mail]:testivate-staging.git HEAD branch: master Remote branch: master tracked Local ref configured for 'git push': master pushes to master (up to date) $ git remote show heroku * remote heroku Fetch URL: [e-mail]:testivate.git Push URL: [e-mail]:testivate.git HEAD branch: master Remote branch: master tracked Local ref configured for 'git push': master pushes to master (up to date) 

I know Heroku is wrong because there are some obvious daytime changes in my views that you can see in my local code and on the staging server, but not in my live application.

For example, compare the back link, which is located correctly here in my middleware application, but not here in my production application.

How do I get Heroku to update my production application as I want?

Thanks,

Stephen.

Answer 1

Are you sure you mean the right branch? Here is the syntax of the actual command:

 git push heroku <the branch you wish to push>:<the branch on the heroku server you wish to push to> 

So if you use

 git push heroku master 

and you check and pass a branch other than master by running git push heroku master , you will git push heroku master your branch without changing master . Run instead

 git push heroku the_branch_i_changed:master 

Answer 2

This is how I made another error with the same result (Ruby on Rails specific):

My new logo image was displayed on my local website, heroku website displayed the old logo. Despite this, I continued to see the message: "do nothing (working directory is clean)."

I forgot to recompile the assets before clicking:

 rake assets:precompile 

Hope this saves someone else when I wasted!