Replies: 1 comment
-
After reviewing the inspector code a bit more, it seems like gitlab will not work out of the box in a similar way to the github string. I suppose the alternatives in my situation are:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
For our graphql inspector use case, we want to validate Pull Requests against production where introspection is turned off. That means we can't point to the graphql endpoint.
Previously, we pointed to github using the format mentioned in the docs of
git:ref:path/to/file
i.e.github:<orgname>/repo/path-to-file
.However, we recently migrated to gitlab and need to point there instead. I've noticed the Gitlab urls are a bit different. There are more levels involved such as
git:owner/subproject/project/repo/path-to-file/etc
. I've tried pointing to gitlab using this similar format and it doesn't seem to work. I get a fetch error. I will also mention I did pass in a Gitlab token which has access to read the repository, so I don't think it is a security issue.Do you have any guidance or docs on if pointing to other git providers or alternative ways of making this work?
Error message:
Beta Was this translation helpful? Give feedback.
All reactions