Composite workflows should support timeout-minutes

[GergelyKalmar]

Select Topic Area

Bug

Body

The following workflow currently fails:

name: Test integrations
on:
  schedule:
    - cron: '8 10 * * *'

jobs:
  run-python-tests:
    name: Run Python tests
    uses: logikal-io/github-workflows/.github/workflows/run-python-tests.yml@v4
    with:
      pytest-options: --fast
    permissions:
      contents: read
      id-token: write
    secrets: inherit
    timeout-minutes: 10

The error: "The workflow is not valid. .github/workflows/test-integrations.yml (Line: 16, Col: 5): Unexpected value 'timeout-minutes'".

You can see the issue in a public repository under https://github.com/logikal-io/stormware/blob/main/.github/workflows/test-integrations.yml.

I would expect timeout-minutes to keep working after refactoring steps into a reusable workflow, which is not the case currently.

[ramonrrp]

Hi!
News from this case? I`m experiencing problems related to this

[scrnjakovic]

This restriction makes no sense whatsoever. Our job on a self-hosted runner cannot run for more than 360 minutes for no good reason at all.

[gladykov]

This limitation really is bad. Because now I cannot directly replace steps with composite reusable steps, and I need to introduce timeout in code.

[ayk33]

Can get some updates on this one? This seems like a strange thing not to support?

[thnk2wn]

It would be great to get this supported as some steps really need it and it hurts to either omit it or not be able to reuse action steps.

Additionally it'd be great to document all the things that aren't supported when migrating to a composite action. For example, we also can't access repo vars or secrets directly. That may make sense for public actions but when it's a private repo and action in same repo it feels silly.

[alamin-floenergy]

any update? we are facing the same issue as well. It would be nice have the timeout-minutes feature for reusable workflows