GitLab support? about jupyterlab-github HOT 9 CLOSED

Hi @jhgoebbert, this plugin is fairly customized to the GitHub API, so it would not be trivial to do. That said, it does look like GitLab provides a reasonably similar API, so it should be possible to port the extension. Porting would involve:

1. Constructing different URLs to hit the different GitLab REST endpoints.
2. The GitHub API returns its own JSON contents models, which we must convert to the kind of contents model that JupyterLab expects. We would also need to do that for the GitLab contents.
3. We would need to swap out the branding images.
4. There will likely be the need to change how we respond to error messages, branding information, etc.

At some point, both GitHub and GitLab will move to a GraphQL-based API, and that will likely make porting it easier.

from jupyterlab-github.

Thanks for your detailed answer, Ian.
GraphQL probably would solve some issues.

Just for other readers:
GraphQL is currently planned for GitLab for 2018-Q2

• https://about.gitlab.com/okrs/
• https://gitlab.com/gitlab-org/gitlab-ce/issues/34754

from jupyterlab-github.

I came across this the other day, which appears to be based on this extension. I don't know how functional it is, but it may be worth investigating.

from jupyterlab-github.

For those interested I created a jupyterlab-gitlab extension based on jupyterlab-github 0.10.0.

I looked at the jupyterlab_gitlab extension mentioned above but it's based on a much older version of the github extension and it didn't fit my needs:

• the user can only be changed in the advanced settings
• files without a “.” in the name can’t be opened
• no server extension

That's why I decided to create a new one based on a recent version of jupyterlab-github.
This is to use at work with our own instance of GitLab.
It might be useful to others.

Thanks to the Jupyter team for the initial extension!

from jupyterlab-github.

Awesome, thanks for sharing @beenje!

from jupyterlab-github.

Wondering if there isn't a way to share most (all of the frontend?) code by abstracting out the api calls (different server extension, same JupyterLab extension).

Just musing out loud...

from jupyterlab-github.

Today, the server extension is not mandatory and all the logic is in the lab extension.
The server is just used as a proxy.
But I guess the logic could be moved to the server extension...

from jupyterlab-github.

from jupyterlab-github.

Closing as there is now a jupyterlab-gitlab extension under the jupyterlab-contrib GitHub organization: https://github.com/jupyterlab-contrib/jupyterlab-gitlab

from jupyterlab-github.