Pull Requests | Issues | v0.3.1...v0.3.2
Features
#68 #70 #93 Enable you to estimate appropriate timeout-minutes per job by the job execution history using GitHub API
workflow_call
ghatm sets 30 to timeout-minutes by default, but the appropriate timeout-minutes are different by job, and it's difficult to decide the appropriate timeout-minutes.
So this release provides the feature estimating appropriate timeout-minutes of each job by the job execution history using GitHub API.
Usage:
ghatm set -auto [-repo <repository full name | $GITHUB_REPOSITORY>] [-size <The number of sample jobs | 30>]
You need to pass a GitHub access token via environment variable GITHUB_TOKEN
or GHATM_GITHUB_TOKEN
.
This feature uses GitHub API.
- https://docs.github.com/en/rest/actions/workflow-jobs#list-jobs-for-a-workflow-run
- https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#list-workflow-runs-for-a-workflow
By default, the feature collects 30 successful jobs for each job, but you can change the number using -size
option.
The feature collects 30 jobs for each job and gets the longest job execute time.
timeout-minutes: The longest job execution time + 10