ci: add timeout-minutes to every workflow job#87
Merged
Conversation
Every job ran without an explicit timeout, so a hung step would hold a runner to the 6-hour default (wasted minutes, delayed feedback). Cap each of the 10 jobs across the 9 workflows with a per-job timeout sized generously over its typical duration — it only fires on a genuinely stuck run, never on a normal (even slow) one: * fast utility jobs (Conventional commits, Dependency review, Dependabot auto-merge): 10 min * build / analyzer / pack jobs (ci, both analyzer dogfoods, release-dryrun): 15 min * heavier jobs (Sonar, CodeQL, the release pack-push): 20 min Config-only change; no behaviour change on a healthy run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
No workflow job had an explicit timeout, so a hung step would hold a runner to the 6-hour default (wasted minutes, delayed feedback). This caps each of the 10 jobs across the 9 workflows with a per-job timeout sized generously over its typical duration — it fires only on a genuinely stuck run, never on a normal (even slow) one.
Type of change
Changes
timeout-minutesadded to every job:Testing
dotnet build FirstClassErrors.slndotnet test FirstClassErrors.slnFirstClassErrors.Analyzers.UnitTests)Not applicable: CI-config-only change, no behaviour change on a healthy run. Verified: all 9 workflow files parse as YAML, and each of the 10 jobs carries exactly one
timeout-minutes(10 total).Documentation
🤖 Generated with Claude Code
https://claude.ai/code/session_01AbXi2ZEaUFeFWodNxdY6Zk
Generated by Claude Code