makkes / gitlab-cli Goto Github PK

Hey can you please add completion for zsh as well ?

I just downloaded onto Debian using the curl method and found that the 'gitlab-cli' example in the animated gif on the repo doesn't work because the command is called 'gitlab' now :-)

Akin to gh pr create, which automatically forks the upstream repository if needed, pushes the current branch, and creates a PR.

Running on intel based macOS bigSur

❯ curl -sSfL https://raw.githubusercontent.com/makkes/gitlab-cli/master/install.sh | sh -s       
Downloading gitlab v3.7.3...
######################################################################## 100.0%##O=#  #                                                                      
install: illegal option -- t
usage: install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
               [-o owner] file1 file2
       install [-bCcpSsv] [-B suffix] [-f flags] [-g group] [-m mode]
               [-o owner] file1 ... fileN directory
       install -d [-v] [-g group] [-m mode] [-o owner] directory ...

However I downloaded the binary and put it manually, no idea about the install command.

I've managed to authenticate to our self-hosted gitlab CE server and get some information out of it, but there doesn't seem to be any documentation of the CLI other than the 'help' output (is that correct?)

It seems like the CLI acts as a 1:1 wrapper around gitlab API v4 requests, so if I want to list all the projects, I have to keep invoking 'gitlab projects --page NNN' until it runs out, similarly for other information like issues. Are there more powerful capabilities of the API that would let it, for example, return all the projects in one command?

I'm not intending to rag on the CLI for not being something it's not, just to understand what it is capable of at present.

4

The fact that commands are comprised by gitlab NOUN VERB has proven to make the CLI somewhat counterintuitive to use while the gitlab VERB NOUN paradigm has proven to be very successful in other projects, such as kubectl.

Therefore, we would like to change the syntax in the following way:

Thanks for your application
Do you know this project https://github.com/xanzy/go-gitlab ?
And this other https://github.com/plouc/go-gitlab-client ?
I think that the first is a good base for your application.

When running gitlab update, the tool should stay within the same major version to ensure backwards compatibility.

Users should still be able to upgrade to a newer major version by providing a flag.

Given that most of the underlying functionality is split out of the actual commands, anyway, there is opportunity to provide importable Go routines for interacting with GitLab instances.

When i do projectsor projects <group> or projects <group>/ nothing is displayed.

Hello, any reason to append -cli to the executable name? We know it’s a CLI tool, since we use it… from the CLI. Typing $ gitlab projects would seem more natural than $ gitlab-cli projects.

Thoughts?

There are no integration tests for this CLI. This will be a huge problem as soon as GitLab changes the API.

I tried the Go install command and it said there were no files

The instructions say as the last resort download the install files, which are listed as gitlab_v4.1.0-alpha.2_windows_amd64 for Windows.

Windows tries to open that with the Windows Store, which is probably not right. What are the extensions? What are the file types? What is the last-last resort?

I'm on Windows 10.

The help for var create doesn't explain possible values for flags and I couldn't really tell from the source what valid values look like.

1. Summary

I can't find, which scopes I need to select for gitlab-cli log in.

2. Details

Documentation:

All commands of gitlab-cli currently require that you are authenticated. To do so you issue gitlab-cli login YOUR_TOKEN. You obtain a personal access token at https://gitlab.com/profile/personal_access_tokens.

No information about scopes, that users needs to select:

Thanks.

The projects command only shows personal projects and I couldn't see a way to view projects from groups you're a member of. It would be nice to have a way to view these from the CLI.

I am trying to access our self-hosted Gitlab server but cannot find the settings applicable in the .gitlab-cli.json file.
Is that even possible?

https://github.com/makkes/gitlab-cli/pull/51/checks?check_run_id=1445009039:

Error: Unable to process command '##[set-env name=GOROOT;]/opt/hostedtoolcache/go/1.15.5/x64' successfully.
Error: The `set-env` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
Error: Unable to process command '##[add-path]/opt/hostedtoolcache/go/1.15.5/x64/bin' successfully.
Error: The `add-path` command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the `ACTIONS_ALLOW_UNSECURE_COMMANDS` environment variable to `true`. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

The Asciinema recording is not viewable.

Currently the only command referenced for issue is inspect.
Would it be possible to add a create command with parameters:

• title
• details

This would make adding issues way quicker than the somewhat complicated process in Gitlab.

Not sure if this is due to inherent pagination in the GitLab API but for a project with over 20 CI/CD vars, only the first 20 are listed.

Plus: Provide it via homebrew.