Bengt Brodersen

regarding your other point, `ℹ First matching configuration will be used.` from top to bottom. Does that help?

@aSemy I haven't found a way to implement your idea with the Action class nor any alternative. Do you have an clue for a solution?

@aSemy I'm totally on your side i switched to Kotlin some years ago also :-), however I was too lazy to convert this project. So yes I am interested in...

I'll try to implement it in Java and then I'll migrate the project to kotlin

your approach would work, however it would lead to a ugly syntax like ```korlin branch(".+") { gitSituation -> new PatchDescription( version = "${gitSituation.ref}") } ```

@aSemy oh that would be awesome.

@aSemy sounds great I was not aware of Gradle Settings plugins

hi @aSemy sorry I was on a long vacation. I'll probably merge it between the holidays.

I've replaced LGTM with CodeQL 876fc5a344e4e9b3e8e10d901c3b7b877372f442

Hi @szpak , thanks for the idea I probably would go for something like this: - `${describe.tag.version.next-patch}` - `${describe.tag.version.next-minor}` - `${describe.tag.version.next-major}`