Benjamin Bertrand

The icon of the Markdown files in the GitLab repository is not changed. It still appears as text icon (not notebook). The GitLab and GitHub extensions defines a Drive that...

There is a [gitLabContentsToJupyterContents](https://gitlab.com/beenje/jupyterlab-gitlab/blob/master/src/contents.ts#L581) function to convert the content from the repo to Jupyter contents. In that [function](https://gitlab.com/beenje/jupyterlab-gitlab/blob/master/src/contents.ts#L640) we force the type to "file". But it still works for notebooks...

The current sdist released on pypi doesn't include any LICENSE. You could use a `MANIFEST.in` file. But it looks like the new way is to use `license_file` or `license_files` in...

@madhur-tandon are you still interested in moving that forward? Otherwise I could have a look.

@marcelotrevisani, I had a quick look and from my understanding, a wheel doesn't include any information about `setup_requires`. I don't see how we could produce a recipe from only a...

> Yes, you are correct, the wheel does not have information about the `setup_requires`, but it does have information about the run requirements and entry points Indeed, there are a...

I'll try to continue what I started and see where it goes.

Hello, No sorry I didn't make progress on that. For my use case, creating the recipe from the sdist is working well. I still would like to finish what I...

For those interested I created a [jupyterlab-gitlab](https://gitlab.com/beenje/jupyterlab-gitlab) extension based on jupyterlab-github 0.10.0. I looked at the [jupyterlab_gitlab](https://gitlab.com/ENKI-portal/jupyterlab_gitlab) extension mentioned above but it's based on a much older version of the...

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...