url.parse is deprecated, and is likely to be removed in a new version of Node.js

Use of the legacy url.parse() method is discouraged. Users should use the WHATWG URL API. Because the url.parse() method uses a lenient, non-standard algorithm for parsing URL strings, security issues can be introduced. Specifically, issues with host name spoofing and incorrect handling of usernames and p

Description of the problem, including code/CLI snippet

Documentation is missing an example how to make use of project import parameters.
The Gitlab-API supports these parameters (name,file,path,overwrite)

Expected Behavior

It would be good to add an example to the documentation (if those parameters are supported)

Actual Behavior

Specifications

• python-gitlab versi

#197 took care of being able to use # at the start of a line, but I just noticed that there isn't a great user flow for editing an issue that already has markdown headings.

1. Create an issue with at least 1 heading
2. Edit the issue with lab issue edit [ID]
3. Make changes and save
4. The issue will now have its heading(s) stripped out

I'm not sure what the best course would be, but

I just had this thought of having a GitHub action for glab.

Do we need that? 🤮

Yeah, I think we do.
Especially for repos on GitHub that are mirrored to GitLab. Maintainers may decide to accept issues and merge requests on GitHub, and write a script that automatically creates the issues and merge requests on GitLab too.
I think there are a lot of other use cases way beyond my imagina

Currently if you try to clone a repository from github and you don't have any ssh keys configured at github, you will fail to clone and get such message:

Fatal error: fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Even Permission denied (publickey). message is not shown.

@guyzmo offered to "suggest a

See scala/scala-xml#359 (comment).

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.

Hi,
Now that we have nested group in gitlab since v9 it would be very interesting to implement it in gitlab-mirrors.
Would be super useful, as we could mirror several git repositories of a unique project to a unique sub group in a base "gitlab-mirrors" group (wow!)

Cheers