-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to deploy to Heroku due to ToS change? #160
Comments
same happens for me |
@AkhileshNS : Any updates on this. I am also facing the same issue my config deploy-staging:
if: github.event_name == 'push' && github.ref == 'refs/heads/main'
needs: build-and-test
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: akhileshns/[email protected]
with:
heroku_api_key: ${{secrets.GH_ORG_HEROKU_API_KEY}}
heroku_app_name: unique-app-name
heroku_email: [email protected]
dontautocreate: true errors: Run akhileshns/[email protected]
with:
heroku_app_name: unique-app-name
heroku_email: [email protected]
dontautocreate: true
branch: HEAD
dontuseforce: false
usedocker: false
docker_heroku_process_type: web
delay: 0
rollbackonhealthcheckfailed: false
justlogin: false
Created and wrote to ~/.netrc
Successfully logged into heroku
› Warning: Our terms of service have changed:
› https://dashboard.heroku.com/terms-of-service
Added git remote heroku
heroku: Press any key to open up the browser to login or q to exit: fatal: 'heroku' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: 'heroku' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Unable to push branch because the branch is behind the deployed branch. Using --force to deploy branch.
(If you want to avoid this, set dontuseforce to 1 in with: of .github/workflows/action.yml.
Specifically, the error was: Error: Command failed: git push heroku HEAD:refs/heads/main
fatal: 'heroku' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: 'heroku' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: 'heroku' does not appear to be a git repository
fatal: Could not read from remote repository.
Error: Error: Command failed: git push heroku HEAD:refs/heads/main --force
fatal: 'heroku' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Please make sure you have the correct access rights
and the repository exists. I have already accepted the TOS in dashboard. I can deploy using |
@AkhileshNS any updates here? I have some workflows that are working and others that are failing due the similar issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A workflow which previously worked now fails. It seems to work but then fails after stating the terms of service have changed, and seeming to ask the user to open a browser to accept them:
It goes on to repeat the issue that heroku is not a git repository, with the main error being "Error: Error: Command failed: git push heroku main:refs/heads/main"
It seems to be able to log in with the justlogin: true. This action used to work, and the API key, app name, and email are in the yml file. Is it possible that it is failing due to the fact the the Heroku terms of service have changed, and it wants a person to manually log in, open the browser, and accept them?
The text was updated successfully, but these errors were encountered: