tektoncd / tektoncd/pipelines-as-code
Check the rate limitation before starting e2e
Open
Nobody has claimed this yet.
bug
ci
good first issue
priority/low
testing
- Dominant language
- Go
- Stars
- 214
- Forks
- 144
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 27
Description
do something like this at the beginning of the workflow pipeline :
[[ $(curl -i -s -H "Authorization: Bearer $GITHUB_TOKEN" -H "Accept: application/vnd.github.v3+json" https://api.github.com/rate_limit|grep x-ratelimit-remaining|sed 's/.*: //') -lt 30 ]] && {
echo "token is rate limited"
exit 1
}
not tested
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the beginning of the e2e workflow pipeline and review how its GitHub API calls are authenticated. Test the proposed shell rate-limit check against the GitHub API, then verify that the workflow stops with a clear message when fewer than 30 requests remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100