question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[FEATURE] Named Versions for Workflows (maybe Actions too?)

See original GitHub issue

Is 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:closed
  • Created 2 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
dylburgercommented, May 17, 2021

@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.

0reactions
dylburgercommented, Jun 6, 2021

@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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Do we have any way to handle version controlling of the code ...
Elton Morais : The only thing I miss on the current control version is the ability to “name” any version I want. And...
Read more >
Workflow actions in SharePoint Designer: A quick reference ...
Use this action to set the status of the workflow. The default options are Canceled, Approved, and Rejected. You can enter a new...
Read more >
How can I reuse a GitHub Actions workflow from the branch I ...
Show activity on this post. I'd like to abstract some of my GitHub Actions with a reusable workflow. `{ref} can be a SHA,...
Read more >
Musings on GitHub Actions Reusable Workflows
Newly released Reusable Workflows allows you to reuse workflows in ... with: dotnet-version: ${{ inputs.dotnet-version }} - name: Restore ...
Read more >
ConvertToFlow App Migrates Process Builder ... - UnofficialSF
This new version of the converter (the original is here) has been updated to convert more kinds of Process Builder workflows to Flows, ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found