-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Allow up to 100 CI checks for CI status command #2704
Conversation
CI seems to be failing to on the |
I'm working on a project that has a complex CI setup, and reaches more than 30. Sometimes `hub ci-status` would report success when it was still pending, which was very annoying. per_page=100 is used in many other queries, and is the maximum that is allowed without paging.
f106450
to
63bdaa5
Compare
I've rebased and force pushed now that CI is working again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! <3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😀
@@ -565,7 +565,7 @@ func (client *Client) FetchCIStatus(project *Project, sha string) (status *CISta | |||
} | |||
sortStatuses() | |||
|
|||
res, err = api.GetFile(fmt.Sprintf("repos/%s/%s/commits/%s/check-runs", project.Owner, project.Name, sha), checksType) | |||
res, err = api.GetFile(fmt.Sprintf("repos/%s/%s/commits/%s/check-runs?per_page=100", project.Owner, project.Name, sha), checksType) | |||
if err == nil && (res.StatusCode == 403 || res.StatusCode == 404 || res.StatusCode == 422) { | |||
return |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [ ]
I'm working on a project that has a complex CI setup, and uses more than 30 CI jobs. Sometimes
hub ci-status
would report success when it was still pending, which was very annoying, because it was only checking the first 30.per_page=100
is used in many other queries, and is the maximum that is allowed without paging.