Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: Error: Command failed: git push heroku HEAD:refs/heads/main --force

See original GitHub issue

Issue Description

Below is the error I received:

And this is my main.yml file:

name: Deploy

on:
  push:
    branches:
      - master

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Install packages
        run: npm install
      - name: Build project
        run: npm run-script build
      - uses: akhileshns/heroku-deploy@v3.11.10 # This is the action
        with:
          heroku_api_key: ${{secrets.HEROKU_API_KEY}}
          heroku_app_name: "git-auto" #Must be unique in Heroku
          heroku_email: "ishaan99ohri@gmail.com"
          procfile: "web: npm start"

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:10 (8 by maintainers)

Top GitHub Comments

1reaction

IshaanOhricommented, Feb 22, 2021

So I figured out the exact problem and the exact solution for this. If we connect the repository on Heroku for automatic deployments, then what happens is that as soon as a commit is pushed, the repository content on Heroku changes and the GitHub Action is also triggered, which makes use of the repository content on Heroku, makes some changes to it and pushes it back to Heroku. In between the GitHub action accessing the Heroku content and pushing it back to Heroku, the content on Heroku changes due to automatic deployment which causes differences in the content, because of which this error arises.

The solution to this is to not enable the automatic deployment on Heroku.

I really feel this is worth mentioning as an important note in the README, therefore I have made the required changes and have generated a PR for the same. Would appreciate merging the PR and closing the issue.

0reactions

IshaanOhricommented, Feb 23, 2021

Thanks for providing the correct information. That was the probable explanation I could think of. My bad. But yeah, the problem was related to Automatic Deployments. Thanks, man!