What would you like to be added?
Some scheduled GitHub Actions workflow jobs should define timeout-minutes.
These scheduled workflow jobs currently do not define one:
.github/workflows/codeql-analysis.yaml: analyze.github/workflows/stale.yaml: stale
I suggest adding explicit timeouts to these jobs, for example:
For stale.yaml, a shorter timeout such as 15 minutes may be enough because it only runs actions/stale.
The repository already uses explicit job timeouts in other workflows, such as .github/workflows/build_tool.yaml and .github/workflows/publish_tool.yaml.
Why is this needed?
Scheduled workflows run without direct user interaction, so a stuck job can occupy a runner until the default GitHub Actions timeout is reached.
Adding explicit timeouts makes these jobs fail faster when they hang and keeps runner usage bounded.
What would you like to be added?
Some scheduled GitHub Actions workflow jobs should define
timeout-minutes.These scheduled workflow jobs currently do not define one:
.github/workflows/codeql-analysis.yaml:analyze.github/workflows/stale.yaml:staleI suggest adding explicit timeouts to these jobs, for example:
For
stale.yaml, a shorter timeout such as15minutes may be enough because it only runsactions/stale.The repository already uses explicit job timeouts in other workflows, such as
.github/workflows/build_tool.yamland.github/workflows/publish_tool.yaml.Why is this needed?
Scheduled workflows run without direct user interaction, so a stuck job can occupy a runner until the default GitHub Actions timeout is reached.
Adding explicit timeouts makes these jobs fail faster when they hang and keeps runner usage bounded.