ci: add timeout-minutes to scheduled workflow jobs
@kunal-yelgate is already working on this.
Since Jun 23, 2026.
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
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:
timeout-minutes: 60
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.