Clement Sam

Hi @ktdreyer, thanks for opening this issue. I will take a look at it. It is also open for anyone who would like to take this up

Hi @okias, thanks a lot for this PR. I love this, however, we announced that this project is officially adopted by GitLab https://github.com/profclems/glab/issues/983#issue-1175723125. All new contributions should be made to...

Since `--description` is a string flag, passing it without argument is an error unless the user passes an empty string `--description ""`

Hi @4thel00z, thanks a lot for this PR. We announced that this project is officially adopted by GitLab https://github.com/profclems/glab/issues/983#issue-1175723125. All new contributions should be mode to the GitLab repo: https://gitlab.com/gitlab-org/cli

@Gaibhne thanks for opening this issue. `glab` supports self-hosted instances. Your second attempt (`glab auth login --hostname 1.2.3.4:10080`) should work fine but the resulting error seems to be a proxy...

During authentication, you selected `https` instead of `http` for the `api_protocol` so the request was served via `https`. Run: ```sh glab auth login --hostname 1.2.3.4:10080 ``` Select `http` for `api_protocol`...

You should be able to leave the git protocol at `ssh`. You can set the `api_protocol` manually with: ``` glab config set -h 1.2.3.4:10080 api_protocol http ```

What I meant was that, instead of using `glab auth login` you can login manually by setting the config values with the `config` command. 1. Add token ``` glab config...

Is the api host the same for the git host? It looks like you have git and the api serving on different ports: 10022 and 10080?? If that's the case,...

Hi @VannTen, thanks for reporting this issue. `glab repo clone` only respects the environment variables for now (I will consider it a bug and fix it). So it whould work...