Better configuration option

[Andre601]

Having to create and edit a TS file feels kinda weird, even if you have a little experience with TS itself.

Instead of having such a file should the config options be defined in a different format, like JSON or YAML, to be a bit more userfriendly.

Additionally should it be configurable, where the file is located (if that isn't a thing already), to allow maintainers the freedom of organizing their repository the way they like to have (i.e. by putting the config in the .github folder).

[anbraten]

Honestly json or typescript is pretty similar 🤔 As you can not write hooks easily in json / yaml those aren't really an option TBF:

plugin-ready-release-go/src/utils/types.ts

Line 42 in 111667f

getNextVersion: (ctx: HookContext) => PromiseOrValue<string>;

Quite a few options can be set using env variables / plugin settings: https://github.com/woodpecker-ci/plugin-ready-release-go/blob/main/docs.md#settings

[Andre601]

I personally dislike that the docs.md isn't explaining all the settings. Only a few (in regards to the config ts file) and then expects the user to know how to read the TS file and how it should be formatted...
Granted, one can assume that someone using Woodpecker may be familiar with such stuff, but it's also not a guarantee either.

What I want to say is, that a bit more verbose explanation would be of great use for the more average user. Maybe a sort of cookbook page could be useful here, listing some examples?

[Andre601]

Also, at the very least should it be made possible to allow setting your own location for the config file, no?
Or alternatively have some options be added to the plugin settings, like the commentOnReleasedPullRequests option (Maybe as a PLUGIN_COMMENT_ON_RELEASE_PRS env variable?).