We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits now shows 35d (not 72h).
(original thread #1054 (comment))
The text was updated successfully, but these errors were encountered:
I have opened a PR for this change (referenced above) - I also question whether or not the change is actually necessary based on the Github documentation - https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes
I guess it is a good backup to ensure the runner is always shutdown after a predetermined amount of time, maybe we do 35 days + 5 minutes instead?
Sorry, something went wrong.
casperdcl
Successfully merging a pull request may close this issue.
https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits now shows 35d (not 72h).
(original thread #1054 (comment))
The text was updated successfully, but these errors were encountered: