-
Notifications
You must be signed in to change notification settings - Fork 59.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jobs.<job_id>.steps[*].timeout-minutes
doesn't describe input < 1
, or give examples
#34685
Comments
For 2, something like my-job:
runs-on: ubuntu-latest
timeout-minutes: 30 from https://stackoverflow.com/questions/59073731/set-default-timeout-on-github-action-pipeline would work well. |
@hamirmahal Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛 |
@nguyenalex836 You're welcome! |
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀 |
@hamirmahal Thank you so much for your patience while our SME team reviewed! 💛 Upon testing, they found that fractional values are unsupported. They advise to add a note that the value of I have added the |
This comment was marked as spam.
This comment was marked as spam.
@nguyenalex836 You're welcome! Would you like any other changes to #34879? |
Out of curiosity, where can I find metrics for https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions? It'd be interesting to see how many views that page gets, and how much usage docs.github.com gets in general. |
Your changes look perfect ✨ getting that merged now!
Let me do some digging, and I'll get back to you! 💛 |
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes
What part(s) of the article would you like to see updated?
timeout-minutes
to a value less than1
, like0.01
.Additional information
No response
The text was updated successfully, but these errors were encountered: