pipe-cd/pipecd

ci: add timeout-minutes to scheduled workflow jobs

Open

#6.902 geöffnet am 7. Juni 2026

Auf GitHub ansehen
 (6 Kommentare) (0 Reaktionen) (1 zugewiesene Person)Go (319 Forks)auto 404
good first issuekind/enhancement

Repository-Metriken

Stars
 (1.329 Stars)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

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