Piotr Krzemiński

Results 112 issues of Piotr Krzemiński

Currently the typings are stored in https://github.com/krzema12/github-actions-kotlin-dsl/blob/main/wrapper-generator/src/main/kotlin/it/krzeminski/githubactions/wrappergenerator/WrappersToGenerate.kt Instead, they could be stored in YAML files, according to this standard: https://github.com/krzema12/github-actions-typing It would allow us to have the same format in...

operational

See https://github.com/krzema12/github-actions-typing/network/dependents Usually we encourage action owners to introduce the typings, but sometimes they introduce them on their own, without letting us know. We could be proactive here, detect such...

operational

Hi! Would you be open for introducing typing for your action's API (inputs and outputs) using https://github.com/krzema12/github-actions-typing/? To see how such typing could look like, see https://github.com/krzema12/github-workflows-kt/blob/main/actions/softprops/action-gh-release/v1/action-types.yml. Some context: I...

Currently the user needs to use either `.writeToFile(...)` or `.toYaml(...)`. This API is clear, but there are several problems: * hard to reuse the workflow if we wanted to call...

enhancement

To be done only when the server-side binding generation is mature enough to recommend using it over the built-in bindings.

Here https://github.com/typesafegithub/github-workflows-kt/blob/77d8c4ebd6c8bbc533a381e9d14c2b9a8992aa34/action-binding-generator/src/main/kotlin/io/github/typesafegithub/workflows/actionbindinggenerator/GenerateActionBindingsCliHelper.kt#L43 we iterate sequentially. Since subsequent iterations don't depend on each other, we can parallelize it. I think processing 5 actions at once is a good starting point. It...

enhancement
good first issue

1. We still use prints instead of proper logging. It doesn't allow us to differentiate logging levels. It would be useful. 2. Some logs lack info, especially now when we...

enhancement

For starters, add a migration guide from the old approach. Later, use the new approach as the default one.

documentation

Ticket on the Kotlin side: https://youtrack.jetbrains.com/issue/KT-63418/

problem

See: * https://kotlinlang.slack.com/archives/C02UUATR7RC/p1674211088336319?thread_ts=1674207463.128059&cid=C02UUATR7RC * https://kotlinlang.slack.com/archives/C02UUATR7RC/p1674215445874089?thread_ts=1674207463.128059&cid=C02UUATR7RC