The Kotlin Advent of Code template project has this really cool GitHub workflow which edits the project files after the new repository is created and deletes itself when complete.
There are a lot of files that need to be updated when a compiler plugin project is created. It would be nice if a workflow could handle many of these automatically. For example:
- Files within
compiler-plugin need to be renamed and relocated based on the desired package and plugin name.
- Files within
gradle-plugin need to be renamed and relocated as well.
- Both files in
META-INF/services need to be updated based on class names and package.
- The group ID in the root
build.gradle.kts file needs to be updated.
- The plugin name and implementation class in
gradle-plugin/build.gradle.kts needs to be updated.
- And probably lots more...
Since there will be multiple pieces of information that need to be provided to correctly update all of these files, maybe a manually triggered workflow would work better?
The Kotlin Advent of Code template project has this really cool GitHub workflow which edits the project files after the new repository is created and deletes itself when complete.
There are a lot of files that need to be updated when a compiler plugin project is created. It would be nice if a workflow could handle many of these automatically. For example:
compiler-pluginneed to be renamed and relocated based on the desired package and plugin name.gradle-pluginneed to be renamed and relocated as well.META-INF/servicesneed to be updated based on class names and package.build.gradle.ktsfile needs to be updated.gradle-plugin/build.gradle.ktsneeds to be updated.Since there will be multiple pieces of information that need to be provided to correctly update all of these files, maybe a manually triggered workflow would work better?