What is the default timeout for a GitHub Actions job if 'timeout-minutes' is not specified?
Select an answer to reveal the explanation.
Short Explanation
GitHub gives each job a 6-hour safety valve by default. If you don't set 'timeout-minutes', a hung job gets cancelled after 360 minutes instead of draining your runner minutes forever.
Full Explanation
The default 'timeout-minutes' for a GitHub Actions job is 360 minutes, or 6 hours, when not specified. If a job exceeds that timeout, GitHub cancels it automatically. Individual steps can have their own 'timeout-minutes'. Some sources cite 60 minutes, but current GitHub documentation gives 360 minutes for GitHub-hosted runners. Self-hosted runners have no enforced default timeout. The 30-minute choice is wrong because it is not the documented default. The 60-minute choice is wrong because it reflects a common misconception, not the current default. The no-timeout choice is wrong because GitHub-hosted jobs do not run indefinitely; the default 6-hour limit prevents billing surprises from hung jobs consuming runner minutes.