fix(ci): drop invalid timeout-minutes from 4 reusable-workflow calls (were parse-rejected/dead) by hyperpolymath · Pull Request #374 · hyperpolymath/gitbot-fleet

hyperpolymath · 2026-07-17T19:45:36Z

What

governance.yml, hypatia-scan.yml, mirror.yml, and secret-scanner.yml each set a job-level timeout-minutes: on a job that calls a reusable workflow via uses:. GitHub does not permit that key on a workflow_call job, so it rejected all four files at parse time — they failed instantly (0s, run titled by raw filename) on every push and never executed a single job.

Net effect on the hub: governance enforcement, hypatia scanning, GitLab mirroring, and secret scanning were all silently disabled.

Evidence

gh run view on a recent run: "This run likely failed because of a workflow file issue."
actionlint (real tool): when a reusable workflow is called with "uses", "timeout-minutes" is not available on all four.

Fix

Remove the invalid caller-side timeout-minutes:. The standards *-reusable.yml workflows already declare timeout-minutes on every internal job, so the caller key was redundant as well as invalid. This matches the already-correct rsr-template-repo pattern, and the upstream hypatia rule missing_timeout_minutes (lib/rules/workflow_audit.ex) already exempts reusable-call jobs — so these will not be re-flagged.

Verification

actionlint on the four files: exit 0, zero timeout-minutes is not available findings remain on the hub.

Wider context

This is the reference fix for an estate-wide shared-fate defect: 84 repos carry the same dead pattern. A scripted, verified sweep of the remaining 83 is proposed separately.

🤖 Generated with Claude Code

…w calls governance.yml, hypatia-scan.yml, mirror.yml and secret-scanner.yml each set `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a workflow_call job, so it rejected all four files at parse time: each failed instantly (0s, titled by raw filename) on every push and never ran a single job. That silently disabled governance, hypatia scanning, GitLab mirroring and secret scanning on the hub. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller-side key was redundant as well as invalid. Removing it restores the four workflows and matches the already-correct rsr-template-repo pattern. The upstream hypatia rule `missing_timeout_minutes` (lib/rules/workflow_audit.ex) already exempts reusable-call jobs, so these will not be re-flagged. Verified with actionlint (real tool): all four files parse clean, exit 0; zero `timeout-minutes is not available` findings remain on the hub. Part of the estate-wide CI cleanup: 84 repos carry this same dead pattern. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#291) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#121) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#21) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#79) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#32) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#85) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#13) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#30) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#78) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#37) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#64) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#45) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#67) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#134) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#75) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#66) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#47) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#32) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#121) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#56) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#45) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#9) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#49) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#42) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#65) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#271) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#46) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#287) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#40) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

…arse-dead) (#211) ## What One or more jobs set a job-level `timeout-minutes:` on a job that calls a reusable workflow via `uses:`. GitHub does not permit that key on a `workflow_call` job, so it **rejected the file at parse time** — the workflow failed instantly (`0s`) on every push and never ran a single job. ## Fix Remove the invalid caller-side `timeout-minutes:`. The standards `*-reusable.yml` workflows already declare `timeout-minutes` on every internal job, so the caller key was redundant as well as invalid. ## Verification `actionlint` (real tool): no `timeout-minutes is not available` findings remain. ## Context Estate-wide shared-fate CI defect across 84 repos. Reference fix: hyperpolymath/gitbot-fleet#374. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

hyperpolymath marked this pull request as ready for review July 17, 2026 19:59

hyperpolymath enabled auto-merge (squash) July 17, 2026 19:59

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(ci): drop invalid timeout-minutes from 4 reusable-workflow calls (were parse-rejected/dead)#374

fix(ci): drop invalid timeout-minutes from 4 reusable-workflow calls (were parse-rejected/dead)#374
hyperpolymath wants to merge 1 commit into
mainfrom
fix/ci-timeout-minutes-reusable

hyperpolymath commented Jul 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

hyperpolymath commented Jul 17, 2026

What

Evidence

Fix

Verification

Wider context

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant