I’m curious, why do the files use the existing .ma...

# github-workflows-kt

[Adam S]

I’m curious, why do the files use the existing .main.kts script context? How about if there was a .github_workflow.kts context, which could provide variables (just like how the .main.kts script provides args)?

[Piotr Krzemiński]

How would you implement a custom context?

[Adam S]

https://kotlinlang.org/docs/custom-script-deps-tutorial.html#create-a-script-definition

[Piotr Krzemiński]

.main.kts is used for simplicity, because it works out of the box and is familiar to most users

[Adam S]

I’m not sure how much improvement it would bring, or whether it’s possible - but I think it could be more ergonomic.

[Piotr Krzemiński]

Happy to see some PoC

[Piotr Krzemiński]

Sound interesting, worth checking out this path

[Adam S]

okay cool, I might have a play around

[Adam S]

I wanted to ask first, in case it was already investigated and wasn’t worthwhile

[Big Chungus]

Main blocker here us that the consumer would need to install yet another tool/plugin to use kts workflows