feat: By default scm github/gitlab/stash/gitea uses force push

[olblak]

I started using 0.75.0-rc.1 and I am really annoyed that I now have to go over all my manifest for a behavior that I feel should be the default.
I would expected for any pipeline relying on a working branch created by Updatecli to be automatically recreated when the based branch is modified.

I already put in place a safeguard for the scm git plugin, because by default it doesn't create a working branch so if only force is set to true there is a risk to accidentally force push changes.
so the following pipeline would trigger an error

scms:
  default:
    kind: git 
    spec:
      url: git@github.com:updatecli/updatecli.git
      force: true

will trigger an error asking to set workingbranch to either true or false to show that the user understand the behavior

scms:
  default:
    kind: git 
    spec:
      url: git@github.com:updatecli/updatecli.git
      force: true
      workingbranch: false

This pull request set force to true for the scm plugins GitLab, Gitea, GitHub, Stash and provide additional safe guards for unclear configuration.

Unclear manifest

scms:
  default:
    kind: github
    spec:
      owner: olblak
      repository: updatecli
      token: '{{ requiredEnv "GITHUB_TOKEN" }}'
      workingbranch: false

Console output

+++++++++++
+ PREPARE +
+++++++++++

Loading Pipeline "/tmp/tt.yaml"
WARNING: Updatecli binary version is unset. This means you are using a development version that ignores manifest version constraint.
WARNING: no git branch specified, fallback to "main"
ERROR: Better safe than sorry.

Updatecli may be pushing unwanted changes to the branch "main".

The GitHub scm plugin has by default the force option set to true,
The scm force option set to true means that Updatecli is going to run "git push --force"
Some target plugin, like the shell one, run "git commit -A" to catch all changes done by that target.

If you know what you are doing, please set the force option to true in your configuration file to ignore this error message.
ERROR: failed loading pipeline(s)
	* "/tmp/tt.yaml" - unclear configuration, better safe than sorry

0 pipeline(s) successfully loaded

SCM repository retrieved: 0


++++++++++++++++++
+ AUTO DISCOVERY +
++++++++++++++++++

ERROR: ✗ no valid pipeline found
ERROR: command failed: no valid pipeline found
[1]    5346 exit 1     ./bin/updatecli diff --config /tmp/tt.yaml

Test

To test this pull request, you can run the following commands:

cd <to_package_directory>
go test

Additional Information

Tradeoff

Different force behavior depending on the scm plugin. I guess the day we align the git plugin with the other ones, we'll be able to also align the force setting

Potential improvement