We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This issue is a follow-up of #3543
The text was updated successfully, but these errors were encountered:
Parse GitLab merge request URLs to identify those in Launchpad
9fd0387
(#3788)
Hi @axosoft-ramint , @eamodio
I have a following question. It looks like GitLab's GraphQL is not able to search for PRs in general. It can does the following:
Now for the Launchpad "get for a user" set of requests is used but retrieving only open ones: state:opened
state:opened
Also there is a REST API endpoint that just searches everywhere, e.g.: https://gitlab.com/api/v4/search?scope=merge_requests&search=flight
What I can do:
For now I'm going to continue with # 3 until we choose another option or find a better solution.
Also, maybe I just wrong about GraphQL possibilities and it can search, and I just haven't found how to do that.
What do you think?
Sorry, something went wrong.
I feel like since what we're doing with GitHub on a search is "search everywhere", we should have equivalent behavior for GitLab. So 3 sounds right.
sergeibbb
No branches or pull requests
This issue is a follow-up of #3543
The text was updated successfully, but these errors were encountered: