Ability to change a run name dynamically (after the run starts)

[alainrodz]

Select Topic Area

Product Feedback

Body

There is the "run-name" which allows an input/constant, but once the workflow jobs starts, you cannot change the workflow name, If the name gets resolved as part of a job action, you are out of luck. There is no api endpoint to rename a workflow run name either. This is very useful. Say you are using GitVersion to resolve the build semantic version, imagine you wanted rename the build to this semantic version. Thanks!

[deadlydog]

You can use the run-name element to dynamically set the workflow run name. It is very limited though as it is only able to access the github and inputs contexts.

I came here to make a similar request as this, to be able to rename the workflow run from a job step. My use case is we want to include the version number (which is determined dynamically during the build workflow run) in our build and deployment workflow run names. Having to click into every workflow run to find out which version it is for (assuming you output it in one of your workflow steps) is a real pain.

+1 to be able to include arbitrary information in the workflow run name from a job step.

[vinmassaro]

Also looking for this feature to add version number to the run name, or other metadata to a run.

[salvianreynaldi]

It'd be fantastic if we can use values from reusable workflow's job outputs in the run-name

[tuyen-vuduc]

It's a +1 from me too. We can change the build number in Azure DevOps. I hope we can do it the same for run-name in GitHub Actions.

[grant-allan-ctct]

I am really hoping for this too.

For my case, I would be able to dynamically change the run-name (so that my runs show up more meaningfully in the Actions tab) if I could

1. while defining run-name, perform string-splitting operations on the input arguments used to trigger the run, or
2. have the ability to tweak the run-name later on while the workflow in progress (and relying on something within the workflow to do the string splitting instead)

But we have neither ability 😞 .

One thing that does save me a little bit of digging as far into the results, based on this technique, was this:

• get my existing job (which is a reusable / "called" workflow) to output the information that I wanted to make more visible
• in my "caller" workflow, create an additional job, and make it dependent on my existing job using the needs keyword
• set the name property of the new job, using the new outputs from my existing job

This makes the useful information visible in the call graph, because the new job is showing the useful information in its name.

[Pablo-Grisafi-Despegar]

If the run name is immutable for some reason, having some way to add info to the Actions screen (lets say a 3rd line, after the run name and the automatic details 'Some workflow #62: Commit [02db591 pushed by someone' ) would be great

[michihuber]

Yes please, want to see the release version that is determined as part of the run in the run list

[GMZwinge]

A multi-line or wrap-around run-name could be useful too when more than one truncated line of information on the run needs to be displayed.