access vars or jobs context in run name or a PUT API for updating run name

Currently the name in workflow run has only access to {{ inputs }} and {{ github }} contexts, which is not very useful as we might want to display additional info which are processed in the job steps.

• either give access to {{ job }} context. It might solve this as it will update name after the job step is completed (from outputs)
• or atleast access the {{ vars }} context, that we ultimately update in some job steps
• If not that then atleast a PUT API endpoint for updating the run's metadata like run-name.

Neither of the above are avaialable 🙂

The users have to go inside every run to check such metadata, because its not displayed in name.

Essentially what differs each run is not just the inputs, but also some processing done from inputs.

For example in my usecase we update our software version for every release run by 1. And we want to display in the run name.

Will appreciate if anyone takes look into this feature ASAP!!!! And many people want this to be fixed.

The issue does not identify a repository file, test, or implementation entry point; it requests changes to GitHub Actions run-name contexts or a PUT API. First determine whether this repository can implement either behavior, then define which proposal is in scope and how run names or metadata should be updated. Done means the selected capability is specified and covered by an appropriate validation path.