#119 Add "useforce" argument to enforce usage of --force

[Hacklone]

Add useforce argument to enforce usage of --force when switching branches to avoid unnecessary double deploy

[Hacklone]

@AkhileshNS: Can you please check this PR, would tremendously help our GH actions :) Thanks

[Hacklone]

Anyone?

[Hacklone]

@AkhileshNS: Is this project still live? There are many open PRs with valuable additions :)

[danilogco]

Hey, @AkhileshNS. Can you check this PR? It would be nice to have it available.

[Gieted]

Would be very useful. My workflow generates some extra files before deploying to Heroku, so it always fails the first attempt.

From https://github.com/myapp/backend
 * [new branch]      preprod    -> origin/preprod
 * [new branch]      prod       -> origin/prod
Created and wrote to ~/.netrc
Successfully logged into heroku
 ›   Warning: Our terms of service have changed: 
Added git remote heroku
 ›   https://dashboard.heroku.com/terms-of-service
To https://git.heroku.com/myapp-test.git
 ! [rejected]        HEAD -> main (fetch first)
error: failed to push some refs to 'https://git.heroku.com/myapp-test.git'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

[Hacklone]

Sent an email to @AkhileshNS but sadly no response. :( Hope he's alright