pipe-cd/pipecd

ci: add timeout-minutes to scheduled workflow jobs

Open

#6 902 ouverte le 7 juin 2026

Voir sur GitHub
 (6 commentaires) (0 réactions) (1 assigné)Go (319 forks)auto 404
good first issuekind/enhancement

Métriques du dépôt

Stars
 (1 329 stars)
Métriques de merge PR
 (Métriques PR en attente)

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.

Guide contributeur