Skip to content
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

ListRepositoryWorkflowRuns doesn't support all query parameters #1497

Closed
acburdine opened this issue Apr 20, 2020 · 1 comment · Fixed by #1498
Closed

ListRepositoryWorkflowRuns doesn't support all query parameters #1497

acburdine opened this issue Apr 20, 2020 · 1 comment · Fixed by #1498

Comments

@acburdine
Copy link
Contributor

It appears that the ActionsService.ListRepositoryWorkflowRuns function doesn't currently support passing in all of the available query parameters for the actual API call, because it's currently using the generic ListOptions struct. The other two ListWorkflowRuns* functions are using a ListWorkflowRunsOptions struct that has all of the supported query parameters listed.

According to the docs it appears all of the options in ListWorkflowRunsOptions are supported by the ListRepositoryWorkflowRuns endpoint. My thinking is that this was either missed in the original implementation, or that Github added support for the additional parameters recently - either way, is there a reason that the function can't be updated to use ListWorkflowRunsOptions?

acburdine added a commit to acburdine/go-github that referenced this issue Apr 20, 2020
closes google#1497 
- update the method to use the more specific ListWorkflowRunsOptions struct
acburdine added a commit to acburdine/go-github that referenced this issue Apr 20, 2020
closes google#1497
- update the method to use the more specific ListWorkflowRunsOptions struct
@gmlewis
Copy link
Collaborator

gmlewis commented Apr 20, 2020

Sounds good to me, @acburdine - thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants