Replies: 2 comments 1 reply
-
Addtional fields are welcomed as well: I would like to add or change the text show in the workflow run, for example here or add additional info on top of the workflow name. For example: we have a different workflow to push to production, and would like to indicate the name of the environment being used for the execution. |
Beta Was this translation helpful? Give feedback.
-
Chiming in with one more use-case: @paritytech needs the |
Beta Was this translation helpful? Give feedback.
-
Current State
The current Actions context metadata contains the following field:
github.workflow
string
This is the only data provided on the source workflow and seems mainly oriented at descriptive, human-readable contexts. The workflow path is useful on its own but is only conditionally available on
workflow_dispatch
events under thegithub.event.workflow
key.Desired State
If possible, it would be useful to break this out into two separate fields:
workflow
orworkflow_name
: same asgithub.workflow
and would still default to the path value if no name were provided.workflow_path
: unconditionally the full path of the executed workflow.This new path field would allow the action to provide a helpful self-link either to the console output or to a self-describing artifact e.g. an audit log.
Beta Was this translation helpful? Give feedback.
All reactions