[FEATURE] Named Versions for Workflows (maybe Actions too?)
See original GitHub issueIs your feature request related to a problem? Please describe.
Every code we save generates a version number. It’s quite common that we get lost on those numbers. In which one I made that specific change? The previous number it’s the last valid version, or it was just some '
or ,
fix? So we have to dig and navigate through many version numbers.
Describe the solution you’d like
It was awesome if we could name any version we want. Not obligatory. Just those we found relevant. The name
would be shown exactly the way the number is. But with the name
instead of the number
. A plus would be the ability to filter the list to show only named versions.
Do you have a workaround? No.
Comparable features in other tools? It would be like a commit comment, BUT simpler, with the ability to name it after creation, when I want, not only on commit.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
@eltonmorais I hear you completely, and it’s very valid feedback. We considered this tradeoff a lot when developing this new version of actions.
Our hope is that we can make the current process even simpler (so that you could author actions in the UI again, for example). I would hope the tooling improvements with the CLI / local dev environment will also improve dramatically over time, so that it’s friendlier to people less familiar with Node.
We certainly don’t have all of the answers yet, but the issues you raised are top-of-mind for us, and I shared this feedback with the team.
@eltonmorais since you mentioned a Git integration would solve this use case for you, I’m going to close this ticket, if you don’t mind. I’ve linked this discussion to that ticket so we can discuss it more when we ship that feature.