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
gitlab.com #6
Comments
As for gitlab.com, it should be compatible with it. Were you having any issues with it aside from not being able to find that command? |
Hi there, All the options on the Tools > GitlabIntegrate are greyed out. My settings are as this:
|
same here |
+1 |
Trying to figure this out myself, but GLI (which I haven't used or looked at in months) no longer seems to work for me on the projects I used to use it on, so I'm having difficulty figuring any of it out. May not be just a gitlab.com issue. |
Worked on this all day today and can't seem to figure out why this happens. My test project works fine if I access the gitlab API directly, but via the package only a non-gitlab.com source works. Using pyapi-gitlab directly in a Python script does not appear to work for either. I suspect there is something in pyapi-gitlab that I'm overlooking that's causing the issue. At this point, the only potential fix I know involves rewriting a significant portion of the plugin, which I don't have the time to do (assuming it would even fix the issue) at the moment. |
Same here |
Same here... probably this is not yet maintained |
I never did find a better fix for it. As far as I can tell, it's a pyapi issue that causes this. Haven't had much time (or, honestly, drive, since I don't use Gitlab or Sublime anymore) to convert all the pyapi calls to raw API calls, which might remedy this. |
It is working for me on GitLab Enterprise Edition 8.11.0-rc3-ee f21518a |
The text was updated successfully, but these errors were encountered: