-
Notifications
You must be signed in to change notification settings - Fork 24
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
Support for a "pulls" query #14
Comments
Hi, thanks for the info. Sounds like a good idea. Currently there's an Do you know if the options currently being used (assignee, milestone, etc.. ) when Also, any ideas if Bitbucket or GitLab have similar options? |
Thanks @sshaw! Yes, I think that would be a great idea to alter the API endpoint, based on the As far as the options for each GitHub API endpoint, it looks like the only ones shared across the two are Sorry, I don't know about Bitbucket and GitLab... maybe the above could be enabled just for |
Yeah seems like the best direction to go. But maybe have specific switches to normalize and/or simplify common options across services. Maybe something like |
|
Any chance you're looking at adding support for a query to the /pulls endpoint, instead of /issues?
It would be great to be able to query for only PRs, and use other switches for /pulls query string parameters such as "base" and "head".
The text was updated successfully, but these errors were encountered: