github workflows kt

Question

github workflows kt <https github com typesafegithub github workflows kt releases tag v1 5 0|v1 5 0 released >

Piotr Krzemiński · Answer

so yeah I encourage you to migrate to the new approach and share your thoughts together with PRs with a successful migration on this channel slightly smiling face

Piotr Krzemiński · Answer

happy to help in case of troubles

Vampire · Answer

biding generation = gt binding generation

Vampire · Answer

To be honest from reading the docs I don t like it too much Of course I understand the intention to need less frequent releases and so on which is also better for consumers with auto update tools but It increases execution time You cannot use different major versions in different places if I got it right Why that extra unrunnable workflow Why not at least giving the actions to the generate call as parameter Current IDE problems with ` Import`

Vampire · Answer

Maybe generate to ` github actions generated` instead or make it configurable if it isn t

Piotr Krzemiński · Answer

> It increases execution time in the current implementation yes It s the cost of the tradeoff We can think how to improve it e g keep generated bindings in the repo and have a cheap method of checking if the bindings need to be regenerated

Piotr Krzemiński · Answer

> You cannot use different major versions in different places if I got it right for now yes it s my intended simplification I didn t want to implement it up front because I wonder if there s any demand for using multiple major versions If you do have such real life scenario let me know I have some ideas how to implement it

Piotr Krzemiński · Answer

> Why that extra unrunnable workflow Why not at least giving the actions to the generate call as parameter To support dependency update bots like Dependabot or Renovate We can consider an alternative API like you suggest something inside `generate action bindings main kts` for those who don t care about the bots

Piotr Krzemiński · Answer

> Current IDE problems with ` Import` shrug something has to happen first either they fix the problems or someone starts using this feature that will increase the priority of fixing the issues smile We can consider waiting longer until it s fixed but keep in mind that waiting longer impacts mostly me as I need to keep the bundled bindings up to date In a month my life will change to an extent that I may not be able to do it regularly so this change in the approach is a part of adjusting to the new circumstances I keep track of the tickets on the Kotlin side in <https github com typesafegithub github workflows kt issues 1090> I encourage you to push JB to fix it sooner

Piotr Krzemiński · Answer

great feedback thank you bow will ticket all these issues soon

Vampire · Answer

gt keep generated bindings in the repo Don t like that either generated things have nothing to do in the repo that generates them imho slightly smiling face Same for the yaml files but that s simply not possible right now without the native integration we hope for gt If you do have such real life scenario Not right now personally but I think there are for sure cases where you might need it slightly smiling face gt for those who don t care about the bots They should at least still notify you about updates I think as they will find the old versions in the generated yaml workflow files gt I encourage you to push JB to fix it sooner Unfortunately nothing I can do besides upvoting which I already did

Piotr Krzemiński · Answer

< LeoColman> would you be open to trying out the new approach Open to your feedback as well

LeoColman · Answer

Absolutely I didn t read your convo tho Let me know what you want to try and I ll do it pronto smile

Piotr Krzemiński · Answer

See the release notes

Piotr Krzemiński · Answer

< Vampire> here are the tracking tickets for the issues ideas you pointed out