-
Notifications
You must be signed in to change notification settings - Fork 26
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
Branch selection dropdown is missing branches #1392
Comments
Ah, the problem for VPN is that the shipit/api/src/shipit_api/admin/github.py Line 116 in f6de1d0
Further, the results returned are sorted by name. So what happened here is that I believe the best fix here is going to be adjust the Github GraphQL query to sort the results by date rather than by name. |
On further investigation, it does not appear to be possible to tell Github to return branches sorted by date via the GraphQL api. So I think we'll have to use pagination to retrieve all branches, then do the sorting in shipit. |
I'm also re-evaluating the "show all branches" part of this issue. I think as long as branches are sorted by date, the odds of the release branches being present are very high. At first I thought the release branches were missing because there were more than 10 branches newer than them.. but that's not the case. |
This endoint currently only fetches up to 100 branches from Github as this is the maximum number of objects you can get from a single query to the GraphQL endpoint. But `mozilla-vpn-client` has well over 100 branches, and the `release` branches were being excluded from the query. Fix this by using pagination until all branches have been returned. Issue: mozilla-releng#1392
This endoint currently only fetches up to 100 branches from Github as this is the maximum number of objects you can get from a single query to the GraphQL endpoint. But `mozilla-vpn-client` has well over 100 branches, and the `release` branches were being excluded from the query. Fix this by using pagination until all branches have been returned. Issue: mozilla-releng#1392
This endoint currently only fetches up to 100 branches from Github as this is the maximum number of objects you can get from a single query to the GraphQL endpoint. But `mozilla-vpn-client` has well over 100 branches, and the `release` branches were being excluded from the query. Fix this by using pagination until all branches have been returned. Issue: mozilla-releng#1392
This endoint currently only fetches up to 100 branches from Github as this is the maximum number of objects you can get from a single query to the GraphQL endpoint. But `mozilla-vpn-client` has well over 100 branches, and the `release` branches were being excluded from the query. Fix this by using pagination until all branches have been returned. Issue: mozilla-releng#1392
This endoint currently only fetches up to 100 branches from Github as this is the maximum number of objects you can get from a single query to the GraphQL endpoint. But `mozilla-vpn-client` has well over 100 branches, and the `release` branches were being excluded from the query. Fix this by using pagination until all branches have been returned. Issue: #1392
I went to create a release for
mozilla-vpn-client
for the first time, but couldn't because the branch dropdown didn't display thereleases/2.20.0
branch. It's also not possible to filter branches by typing into the input.Ideally, this dropdown should contain all branches and it should be possible to type into the input, causing displayed branches to be filtered in real time.
I'm not 100% sure if this blocks VPN or not, I think there may be a way to restrict which branches show up there via the configs, so I'll investigate this avenue first. But as a general feature, this issue would be nice to have regardless.
The text was updated successfully, but these errors were encountered: