Filter repositories by name


#1

With the Oauth2 api, I was able to filter my repositories being returned with the q= query param. With the new integrations /installations/repositories route, q is not working (per_page and page are however). I couldn’t find any documentation on this, so am wondering if this is currently possible?


#2

Hey @anuccio1 :wave:. I’m not sure I understand which q parameter you’re referring to when you say you used it in the “OAuth2 API” – can you share a link to the section of the documentation which documents the API endpoint you were using and that q parameter so that we can understand what you were using before exactly?

To be clear, the endpoint in question (for listing installation repositories) doesn’t support such a parameter currently. Could you share more details about how exactly you’d like to use such a q parameter if it existed – in what way exactly would you like to filter repositories that the installation has access to and in which use-cases would that be helpful to you?


Request for support of OAuth scopes `user` / `user:email`
#3

Sure!

From the docs: https://developer.github.com/v3/search/ :

The q search term can also contain any combination of the supported repository search qualifiers as described by the in-browser repository search documentation and search syntax documentation:

I was wondering if something like this can be used for the /installations/repositories endpoint (maybe I’m missing something in the docs)?

In my front end, I have a paginated (10 per page), full list of users repositories, that also contains a search filter (q parameter in this case), and as I migrate to the Integrations API, it would be extremely beneficial if I was able to do this (as well as order and sort)

This is currently blocking me from moving forward with the migration, as implementing front end filtering/sorting would be a major performance hit

per_page and page query parameters still work, so that’s great!


#4

Thanks for explaining, @anuccio1

I was wondering if something like this can be used for the /installations/repositories endpoint (maybe I’m missing something in the docs)?

No, not currently, and I’m not aware of plans for adding that feature to that endpoint in the near future. The advanced filtering features are limited to the Search API since that API is backed by special infrastructure which allows that.

Perhaps we can enable the Repositories Search API endpoint for integrations as well, so that you can use that endpoint and the advanced filtering, but I can’t say when that might happen. I’ll definitely mention it to the team to consider for the future, and if it’s added – we’ll followup here.

Thanks for providing feedback.


#5

Enabling the repositories search API endpoint would be awesome! I think this would be very beneficial to a lot of other people as well


#6

@izuzak Any update on this? A little more perspective…

We regularly receive messages from potential customers that complain about the amount of write access permission our app requests, when all we really need is read access to user info, repositories, and pull requests. Without the Github integrations API, we can’t do this however.

Not being able to filter the results from /installations/repositories is a major blocker for us, that is preventing our business from moving forward with using the integrations API. Either adding this feature, or opening up the search/repositories endpoint would be a HUGE value add to us, and I’m sure many others. Please consider adding this feature!

Thanks!


#7

Thanks for sharing your thoughts, @anuccio1.

Any update on this? … Please consider adding this feature!

No, there are no updates. As I mentioned before – we’ll followup here as soon as there is any news. The team is considering this, but I can’t say when it might happen – it might not happen in the near future.


#8

This is also a big time blocker for my team as well. We rely on the search filter feature for our UI.


#9

Thanks for expressing interest, @Cmlynars – I’ve passed your feedback along to the team as well. :thumbsup:


#10

+1 same thing here. That’s one of the issues that prevents us from migrating to Github Apps.

IMHO it is related to this other issue that was just opened.


#11

We regularly receive messages from potential customers that complain about the amount of write access permission our app requests, when all we really need is read access to user info, repositories, and pull requests.

Exactly! This is the use case for many continuous integration tools.


#12

Just wanted to add that filtering/searching would also be extremely useful for the GET /user/installations/:installation_id/repositories route as well!


#13

Just wanted to mention that the team has enabled the Search Repositories API endpoint for GitHub Apps:

https://developer.github.com/v3/search/#search-repositories

We hope that helps, but if there are still specific use-cases that are not covered by this – please clearly explain them in a reply (in as many details as possible) and I’d be happy to pass them along to the team.