git push heroku master says “Everything up-to-date

问题:

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!!

回答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

回答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

回答3:

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

回答4:

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.

回答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!

回答6:

Try:

heroku status

This returned the following, which confirmed that the problem was with the heroku API (and not with my app!):

"The API is experiencing delays. This may result in delays with adding new domains, new releases, and other such actions. Currently, engineers are investigating the issue."

回答7:

When this happens, I push previous commit hash like:

git push some-heroku-app-name ee3bca189acec89f5e9b098692ab6cee386a8f25:master --force

Then I re-push master like this:

git push some-heroku-app-name master:master

回答8:

I know, I know, silly, but it happened to me so I'm leaving a warning to others: make sure the app you're pushing to is the same app you're checking for changes.

In my case I was pushing to staging and then running a shell on production and not understanding why the static files didn't change.

(It started with a real issue where static files didn't change when I pushed a new version, but it was probably a one-push fluke, and it only kept me going in circles for another hour because I was testing the wrong app.)

回答9:

If you're using Java, don't forget to rebuild the project before pushing.

In case of Gradle:

gradlew clean install

回答10:

had the same issue, what worked for me was: make a commit with a random message and then push

git commit -m"random message"

git push heroku master

回答11:

My executable name had changed but I forgot to change the name in my Procfile. So while all the files were updating correctly in heroku, the same old executable was running. I used heroku local from the command line to help track that issue down.

回答12:

Same issue, I added a remote to my local repository with the heroku git:remote command and then pushed it.

heroku git:remote -a your-heroku-app

git push heroku master