timeout-minutes should allow for inputs parameter.

Describe the bug step/job timeout-minutes only supports number and the runner will not run the workflow with an configurable inputs timeout.

timeout-minutes: ${{ inputs.test-timeout }}

To Reproduce

name: DotNet Test

on:
  workflow_call:
    inputs:
      test-timeout:
        required: false
        type: number
        default: 10

jobs:
  test:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Test
        timeout-minutes: ${{ inputs.test-timeout }}
        run: |
          dotnet test

Expected behavior With reusable workflows I would hope that I was allowed to pass a timeout-minutes as configurable.

Runner Version and Platform

N/A

What’s not working?

inputs.test-timeout specshell/.github/.github/workflows/dotnet-build.yml@main (Line: 98, Col: 26): Unexpected value '${{ inputs.test-timeout }}'

Job Log Output

N/A

Runner and Worker’s Diagnostic Logs

N/A

[jetersen]

great that a workaround exist but that just shows it should also allow inputs

[ChristopherHX]

I thought this was just documentation bug like for concurrency ( which accepts inputs, even if the documentations tells the opposite ), but you are right the official actions service blocks inputs as valid context and refuse to process your workflow.

Simple Workaround via matrix

name: DotNet Test

on:
  workflow_call:
    inputs:
      test-timeout:
        required: false
        type: number
        default: 10

jobs:
  test:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        test-timeout:
        - ${{ inputs.test-timeout }}
    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Test
        timeout-minutes: ${{ matrix.test-timeout }}
        run: |
          dotnet test

The actions/runner accepts and runs your job with inputs in timeout-minutes, I tested it