@dogboydog,

Yes, currently GitHub does not automatically create environment variables for the inputs of the ‘workflow_dispatch’ trigger.

If you want to use the inputs as environment variables in the workflow, you can set the inputs as the workflow global environment variables via the ‘env’ key.
For example:

on:
  workflow_dispatch:
    inputs:
      log_Level:
        description: 'Log level'
        required: true
        default: 'warning'
env:

INPUT_LOG_LEVEL: ${{ github.event.inputs.log_Level }}
jobs:

job1:

runs-on: ubuntu-latest

steps:

- name: Print input

run: echo "The log level is $INPUT_LOG_LEVEL"

However, as mentioned in the docs, you also need to note that:

When more than one environment variable is defined with the same name, GitHub uses the most specific environment variable. For example, an environment variable defined in a step will override job and workflow variables with the same name, while the step executes. A variable defined for a job will override a workflow variable with the same name, while the job executes.

If your projects really need the feature that GitHub can automatically create environment variables for the inputs of the ‘workflow_dispatch’ trigger, I recommend that you can directly report a feature request here.
That will allow you to directly interact with the appropriate engineering team, and make it more convenient for the engineering team to collect and categorize your suggestions.