Jean-Michel Fayard

Possible solutions (incomplete list) 1. jitpack was based on the idea that you may want to deploy any commit, any branch, so that's related to what we want to achieve...

Via an environment variable, would just have to check which one exactly https://github.com/krzema12/github-actions-kotlin-dsl/blob/a96cfa53a7355a274e73a5831a35a34d5d45810a/library/src/main/kotlin/it/krzeminski/githubactions/dsl/expressions/contexts/EnvContext.kt#L118-L127

Do a code review and find the functions without side effects that are part of the functional core. If they are tested, add an annotation `@TestedBy("SomethingTest")` If they are not,...

@LouisCAD I commented on your idea to have something independant from Gradle here https://github.com/jmfayard/refreshVersions/issues/586 I still think there is no issue with adding Kotlin Script support in the current codebase....

That's strange, please reopen if you get the issue again

Possible solutions: - Let lots of issues opened but focus on a project with a sub-selection of issues - Identify what are core features that define the essence of refreshVersions...

@LouisCAD what's your opinion about GitHub stale bot? https://github.com/apps/stale

Possible solutions - do nothing - keep two plugins but identify better "bounded contexts" - just merge everything in one plugin

@LouisCAD added this comment in another PR > Also, a general thought I had for a while: > We probably want to not depend on being a Gradle plugin for...

**Issue 1 and issue 3** can be resolved by having versioned documentation: two folders `docs/main` and `docs/release` that will be merged just before the release. **Issue 3** can be solved...