Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Heroku push gets rejected

Tags:

git

heroku

I am having problem in pushing my master branch to heroku. I am using the following command:

git push heroku master

Error that I am encountering-

Counting objects: 114, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (112/112), done.
Writing objects: 100% (114/114), 335.40 KiB | 0 bytes/s, done.
Total 114 (delta 0), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Failed to detect set buildpack https://codon-buildpacks.s3.amazonaws.com/buildpacks/heroku/php.tgz
remote: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
remote:
remote:  !     Push failed
remote: Verifying deploy...
remote:

remote: !       Push rejected to skyconfapp.
remote:
To https://git.heroku.com/skyconfapp.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/skyconfapp.git'

I even visited Heroku's link https://devcenter.heroku.com/articles/buildpacks#detection-failure and tried to implement every method that they have mentioned but nothing seems to be working for me.

Can someone please assist?

like image 872
Aakash Thakur Avatar asked Sep 01 '16 09:09

Aakash Thakur


People also ask

Why does git push get rejected?

A commit gets rejected and causes a failed to push some refs to error because the remote branch contains code that you do not have locally. What this means is that your local git repository is not compatible with the remote origin.

How do I push to Heroku again?

To deploy your app to Heroku, use the git push command to push the code from your local repository's main branch to your heroku remote. For example: $ git push heroku main Initializing repository, done.


1 Answers

If you are trying to push a nodejs app and you are getting this error, this could be because you are not specifying node version. I was having this error and it was being caused because I was not specifying "engines": { "node: "8.2.1" }

You can have more details here: https://kb.heroku.com/why-is-my-node-js-build-failing-because-of-an-invalid-semver-requirement

like image 112
freeman76 Avatar answered Sep 23 '22 12:09

freeman76