First of all, thank you for the Fly.io! I wish you good traction and stable growth!
One way to achieve that is developers' adoption. And these actions are good example of caring about us, developers.
But I humbly plead for more.
There is project krzema12/github-workflows-kt that allows you to write action using Kotlin DSL, a statically typed language, preferred by some over the YAML. It doesn't require action's authors to change anything in their actions to be supported. Only types could be optionally provided, but it's not an issue yet.
One thing that this project requires, however, is the existing of major version tags in the actions it supports. Examples are:
You got the idea, a v3 tag always points to the latest v3.x version, whatever it is. It first points to the v3.0.0, but then you release v3.0.1 and move the v3 to point on it, then you release v3.1.0 and update the v3 again, etc…
Can you please add this major version tag in this repository? Thanks!
First of all, thank you for the Fly.io! I wish you good traction and stable growth!
One way to achieve that is developers' adoption. And these actions are good example of caring about us, developers.
But I humbly plead for more.
There is project krzema12/github-workflows-kt that allows you to write action using Kotlin DSL, a statically typed language, preferred by some over the YAML. It doesn't require action's authors to change anything in their actions to be supported. Only types could be optionally provided, but it's not an issue yet.
One thing that this project requires, however, is the existing of major version tags in the actions it supports. Examples are:
You got the idea, a
v3
tag always points to the latestv3.x
version, whatever it is. It first points to thev3.0.0
, but then you releasev3.0.1
and move thev3
to point on it, then you releasev3.1.0
and update thev3
again, etc…Can you please add this major version tag in this repository? Thanks!
cc: @krzema12 context: https://github.com/krzema12/github-workflows-kt/issues/595