-
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
Push rejected to ***. #127
Comments
add this line beforce uses: akhileshns/[email protected]
|
Lines 223 to 233 in 79ef2ae
I read the source code of this project and found that regardless of whether you have set the value of dontuseforce in the code, the value of this variable dontuseforce will be overwritten to true. Only after this code runs and reports an error, the value of this variable dontuseforce will not be overwritten, even with the original value of the variable. The error message in the first picture is misleading, you should actually look at the error message in the second picture. |
I've got the same issue. |
We were having a similar issue (if not the same). Turns out we forgot to add our bot account to the Heroku application (with Deploy access). Doing that, plus the below name: Deploy
concurrency:
group: deploy
cancel-in-progress: false
on:
push:
branches:
- master
jobs:
deploy:
name: Deploy
runs-on: ubuntu-latest
timeout-minutes: 20
steps:
- name: Checkout code
uses: actions/checkout@v3
with:
fetch-depth: 0
- name: Deploy code
uses: akhileshns/[email protected]
with:
heroku_api_key: ${{secrets.HEROKU_API_KEY}}
heroku_app_name: "sample-app-name"
heroku_email: "[email protected]"
team: "sample-team"
dontuseforce: true
dontautocreate: true Hope this helps someone. |
Make sure you regenerate your Heroku API key. It helped in my case. |
The text was updated successfully, but these errors were encountered: