git push heroku master says "Everything up-to-date", but the app is not current

git github heroku push git-push

61,108

Solution 1

Kindly confirm your current branch is master.

 git branch

If the pointer is not pointing the master, then check out to master branch

git checkout master

Commit your changes and try to push to heroku

git commit -am "xxxyyzzz"    
git push heroku master

Solution 2

When you run git push heroku master, git is assuming that you are pushing from master, so if you changes are in other branch, you will try to push your master branch without changes.

You have two options

1.Merge your changes with master and push them.

Commit your changes in your actual branch, then merge them with master

git commit -a - m "your messages"
git checkout master
git merge your_feature_branch
git push heroku master

2.Push your changes from your actual branch

git push heroku your_feature_branch:master

Solution 3

I had a similar issue and by no means my changes were visible on heroku. To reconfirm myself I even took a clone from heroku and it was obviously up to date.

I could resolve my issue only by following this approach:

Step 1: Make a new branch from master

git checkout -b new_branch

Step 2: Just add a comment in any file to make a new commit and then:

git add .
git commit -m "Just a test commit to push new branch to heroku"

Step 3: Push the new branch to heroku.

git push heroku new_branch:master
heroku restart

You could now see your changes successfully on heroku.

Solution 4

I'm willing to bet you've forgotten to run git add . followed by git commit -m 'xyz'?

Solution 5

Even though this is an old issue, I wanted to update with what worked for me (a newbie) should anyone else run into this:

After following the instructions here (from Hudson), what finally did the trick for me was doing a "git pull" after checking out the "master" branch. Perhaps "git push heroku master" pushes out only the local branch of master?

Of course, this assumes all required changes have been correctly merged into your master. I hadn't pulled from master on my local since the project set up because all merges (from development to master) were handled on GitHub and I had been working on new branches that were later merged with development.

So, to restate steps above from Hudson:

git checkout master

git pull

(here, I updated README to have a change to commit, like "Heroku deploy [date, time]"

git add .

git commit -am "xxxyyzzz"

git push heroku master

heroku run rake db:migrate

heroku restart

Good luck!

View more solutions

61,108

Darkmatter5

Updated on April 28, 2022

Comments

Darkmatter5 about 2 years
I have an app on Heroku that is running old code. I've made a small change and committed the change. I then ran
```
git push heroku master
```
It'll say
```
Fetching repository, done.
Everything up-to-date
```
But if I go and look at the app, it's all old code. I did revert the site back to another version in Heroku about 15 days ago, but pushed updates to it since then and they worked.

Why is heroku not getting the most current files from my github repository? Is there a way to just reset the app and push the files from github again? I have production data in the database so I do NOT want to touch it.

Thanks in advance!!
- Ben over 9 years
  
  Same problem here. Did you ever figure it out? Answers offered here are obvious things that I've already tried to no avail. @Darkmatter5
- Clarity almost 4 years
  
  Answers say that I might be on another branch, but I'm experiencing the same problem and my branch is master. Locally I had changed, successfully deployed them on heroku, and git says that there is no difference between local and heroku while changes were NOT actually showing (the browser still displays old version before deploying). I've cleared both client and server caches and the problem persists.
Danny over 9 years

git push heroku yourlocalbranch:master if you want to push your local, non master branch to heroku master
Angel S. Moreno over 9 years

Came here with the same issue @danny cleared up hudson's solution.
RegarBoy over 7 years

Heheheh, this made me laugh. After coding three days and night for fixing little things, I forgot to add and commit my code
dennispreston over 6 years

Same issue for me, I hadn't pulled the master branch after pushing another branch and merging.
Markus almost 6 years

I used this when needed to rebuild after changing the build pack on heroku. You probably need to add --force to the first command.
Vladimir Djuricic almost 6 years

@Markus Actually, I never needed "--force". It doesn't hurt to have it so I've updated my answer. Thx!
abagh0703 almost 6 years

Don't know why you got a downvote... I had the same issue but with a React project. Running webpack -p --progress --config webpack.config.prod.js (where the last arg is the name of your webpack config file) and then commiting & pushing solved the issue for me.
Sunny over 5 years

This git push heroku new_branch:master helped
mithushancj almost 4 years

Thanks for this. Worked like a charm. Didn't know this was possible to push one branch to another.
Clarity almost 4 years

What if the current branch is master but I still have the problem above?
Clarity almost 4 years

It says that "Everything up-to-date", but the problem persists.
Djesu over 2 years

Your solution did the magic!!!
DC1477 over 2 years

This was my problem. I did a git remote -v to check URLs for my "heroku" (production) remote and my "staging" remote, and they were both the same staging url. So I was pushing to staging twice. I deleted the production url and added the correct remote url from my heroku dashboard to my local app. Thanks!