Graphql repository query fails to redirect in some cases #24731
-
As per Inconsistent handling of moved repositories using API v4 the repository query is supposed to redirect when a repo has been moved. Indeed the examples in that thread do work, however I have an example that does not work.
The redirect does work when accessing from a browser or from the v3 api, however it does not work from the graphql api
produces:
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Is encourage you to file a bug: |
Beta Was this translation helpful? Give feedback.
-
I’m getting the same error with @canuckjacq tagging someone in staff, apologies if this is not the right way to do it, but I could not find a way to file a bug from the link above 😦 |
Beta Was this translation helpful? Give feedback.
-
@jsoref Thanks, I have no raised a support ticket. FWIW, it is very unclear if this is the right way to report a bug. All you get is |
Beta Was this translation helpful? Give feedback.
-
Github support said that this is failing as the case is incorrect. In my example it should be I have suggested that this is a bug as in reality org / repo names are case insensitive, and the graphql api should be case insensitive like the web interface and the v3 api. |
Beta Was this translation helpful? Give feedback.
-
GitHub support notified me that it is fixed. This is now working for me 🥳 |
Beta Was this translation helpful? Give feedback.
GitHub support notified me that it is fixed. This is now working for me 🥳