<@U01681FLZC2> I’d like to continue the discussion on a custom script context: <https://kotlinlang.s...

# github-workflows-kt

[Piotr Krzemiński]

@Adam S I’d like to continue the discussion on a custom script context:
https://kotlinlang.slack.com/archives/C0B8MA7FA/p1676989225653899?thread_ts=1676985449.906609&amp;cid=C0B8MA7FA

could you elaborate how it could be achieved? the simplicity of the current approach is that it just works by specifying the shebang, no extra stuff is needed. I’m wondering how the API of the library would have to be changed for this to work

[Adam S]

we previously discussed it here https://kotlinlang.slack.com/archives/C02UUATR7RC/p1667932621581649

[Piotr Krzemiński]

right, thanks! we concluded in a similar way

[Adam S]

I'm not sure how feasible it is to implement. I remember we looked into it and while I think it's possible according to the docs, it would still be a lot of work

[Piotr Krzemiński]

yep, the benefits don’t seem to outweigh the cost just yet

[Adam S]

I think the IJ plugin would basically automatically add the GitHubWorkflowsKtScriptContext in Intellij

[Piotr Krzemiński]

what about calling the .<something>.kts from outside of IntelliJ?

[Adam S]

and then you could have my-workflow.workflow.kts

[Adam S]

no idea 🤷‍♀️

[Adam S]

so the shebang at the moment is kotlin.exe or something, right?

[Adam S]

that bundles the .main.kts scripting context

[Piotr Krzemiński]

https://github.com/krzema12/github-workflows-kt/blob/8a9fcc013a2d723025b92326e782acf14f69a526/.github/workflows/build.main.kts#L1

[Piotr Krzemiński]

#!/usr/bin/env kotlin

[Adam S]

so you'd need to make your own gh-workflow.exe that extends kotlin.exe and also bundles GitHubWorkflowsKtScriptContext

[Piotr Krzemiński]

doesn’t sound like fun 😅

[Piotr Krzemiński]

because this own executable would have to be deployed somehow

[Adam S]

haha, that depends on how much free time you have

[Piotr Krzemiński]

right now oscillating around 0 😂

[Adam S]

I think it's not worth it for something that can basically be emulated by defining some function in the lib

fun workflow(block: GitHubWorkflowsKtScriptContext.() -> Unit) {}

and then in the script, you've got the context

workflow {
  ...
}

[Adam S]

my point with mentioning a custom scripting context is that I think it'd be worth keeping a tally of things that need an IJ plugin, because maybe one day the scales will tip over!