Activity

1. jmfayard

   added

   enhancementNew feature or requestNew feature or request

   on Sep 28, 2022
2. jmfayard

   added this to the v1 (stable) milestone on Sep 28, 2022
3. jmfayard commented on Sep 28, 2022

   

   jmfayard

   on Sep 28, 2022

   ContributorAuthor

   More actions

   Some note on the Slack thread on what the executable could do

   • detekt if Kotlin is already installed, else tels you to open https://kotlinlang.org/docs/command-line.html
   • list all .github/workflows/*.kts available
   • maybe automatically chmod +x because this shit is boring
   • check which input and output files have changed
   • runs the one that needs to be modified
   • maybe suggest to install a git-prepush hook? (I'm not a fan)
4. jmfayard commented on Sep 28, 2022

   

   jmfayard

   on Sep 28, 2022

   ContributorAuthor

   More actions

   Some note on how to build the CLI tool

   I have some experience with it due to https://github.com/jmfayard/kotlin-cli-starter

   And my suggestion will sounds surprising but I would recommend to implement the script with Kotlin/JS

   Why? Because distribution on native and on the JVM sucks.
   On the other hand everything is in place with node.js/npm
5. jmfayard

   changed the title [-]Create a Kotlin executable to improve overallall developer workflow[/-] [+]Create a Kotlin CLI to improve overallall developer workflow[/+] on Sep 28, 2022
6. jmfayard

   changed the title [-]Create a Kotlin CLI to improve overallall developer workflow[/-] [+]Create a Kotlin CLI to improve overall developer workflow[/+] on Sep 28, 2022
7. JavierSegoviaCordoba commented on Sep 30, 2022

   

   JavierSegoviaCordoba

   on Sep 30, 2022

   Last edited by JavierSegoviaCordoba

   More actions

   I haven't thought about this in a more profound way, but integration with Gradle should be great.

   I don't know the current implementation details and names so I will create some ones.

   For example, if the API exposed is similar to how Gradle tasks work, I.E. an interface has to be implemented to create a workflow file, I would expect something like:

   fun interface GitHubActionKotlinDSL {
       fun GitHubDSL.run()
   }

   Implemented in an included build:

   val fooWorkflow = GitHubActionKotlinDSL {
     // implement the foo workflow with the DSL here
   }
   
   val barWorkflow = GitHubActionKotlinDSL {
     // implement the bar workflow with the DSL here
   }

   And the Kotlin Plugin applied (root project):

   plugins {
       id("gha-dsl-gradle-plugin") // whatever name
   }
   
   gitHubActionsKotlinDSL {
       workflows.set(listOf(fooWorkflow, barWorkflow))
   	// or
       workflows(fooWorkflow, barWorkflow)
   }

   A Gradle task with whatever generateGhaDsl name will be attached to the assemble task.

   Another advantage is, those foo/bar workflows can be published to MavenCentral and added to any Gradle project too.
8. jmfayard commented on Sep 30, 2022

   

   jmfayard

   on Sep 30, 2022

   ContributorAuthor

   More actions

   @JavierSegoviaCordoba writing a Gradle plugin is possible
   the issue I see is that if github-actions.kts becomes popular enough,
   we will have people using lots of different build systems.
   Could be maven.
   Could be a guy doing TypeScript or Rust at the moment but who also knows a bit of Kotlin and prefer it over YAML
   etc.

   👍React with 👍1Reacted by Javier Segovia Córdoba
9. krzema12 commented on Jun 2, 2023

   

   krzema12

   on Jun 2, 2023

   Member

   More actions

   It would be nice to have this, but I guess it's not needed for v1.
10. krzema12

    removed this from the v1 (stable) milestone on Jun 2, 2023
11. jmfayard commented on Jun 3, 2023

    

    jmfayard

    on Jun 3, 2023

    ContributorAuthor

    More actions

    For https://github.com/typesafegithub/yaml2kotlin I'm entirely focused on the web app solution, not on the CLI

    👍React with 👍1Reacted by Piotr Krzemiński