Forgejo actions are a near drop-in replacement for GitHub actions. This
commit changes the action.yml file to make the forge configurable. This
allows using the action with forgejo instances.
Changes made:
- Introduce a `forge` input and pass it as the value of the `--forge`
flag.
- Introduce `api-url` input and pass it as the value of the `--api-url`
flag. This is required to configure the API URL of the forge. If the
action is used with GitHub Actions it is simply ignored.
- Pass `inputs.token` as value to the `--api-token` flag. This is
required as the forgejo client does not respect the `GITHUB_ACTION`
environment variable.
- Introduce `owner` input and pass it as the value of the `--owner`
flag. As this was not passed before the default is set to `""`. In
theory it could be set to the value of `github.repository_owner`.
- Introduce `user` input and pass it as the value of the `--user`
flag. As this was not passed before the default is set to `""`. GitHub
Actions does not seem to provide a convenient way to get the
repository without the owner. As such keeping it at `""` for the
default is safest.
Increase the number of code blocks backticks to 4 for the release note prefix and suffix, to allow users to embed their own code blocks using only 3 backticks.
This change reverses the responsibility for which files the updaters are
run on. Now each updater can specify the list of files and wether the
files should be created when they do not exist yet. This simplifies the
handling of each update in releaserpleaser.go, as we can just iterate
over all updaters and call it for each file of that updater.
Also update the flags to allow users to easily define which updaters
should run.
In the CI/CD component, make the jobs `needs` setting configurable
through an input and change the default to `[]`. This will cause the job
to run immediately.
Co-authored-by: jo <ljonas@riseup.net>
