Live data from Hacker News

Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

github.com

61–70 of 76 posts

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#61
Similar:

FWIW, a colleague at Red Hat recently began this upstream project, Bichon[1], to manage Git Lab merge requests from the shell:

"Bichon provides a terminal based user interface for reviewing GitLab merge requests. As well as an efficient keyboard based interaction model, it will allow for off-line code review caching information until reconnected to the network."

        - - -
The interface is loosely modeled after the `mutt` email client; but it's a ground-up implementation.

From what I learned (from a test spin; I'm a long-time `mutt` user myself), Bichon is not aiming to build a custom terminal-only workflow: it is mainly aims to provide an alternative to web UI. IOW, it's not an either/or—command-line and Web UI are supposed to play well together.

[1] https://gitlab.com/bichon-project/bichon/

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#63

My new hobby is installing vanilla Gitlab CE on a vanilla server and waiting until it crashes the whole thing. Takes something between 8 to 36 hours. The server is completely gone, no ping, no ssh. It takes frantic remote power button pushes to even turn it off. Afterwards I reconfigure various config lines and repeat.

I mean this with no judgement: that is a weird hobby. Is there a reason you do that instead of fixing gitlab or just using something else? Either of those would seem more satisfying to me.

I doubt that they meant it literally. May have been a reference to the xkcd “my hobby” strips. See https://www.explainxkcd.com/wiki/index.php/Category:My_Hobby

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#64

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

I suspect due to the sheer number of internal deploys, Gitlab does not always get the exposure warranted. My work place is switching from internal Gitlab/gitlab-runners to external gitlab.com + internal gitlab-runners. We are very happy with both scenarios, but neither gains Gitlab any exposure.

you can create a merge request as well using only git, gitlab support it

  git push -o merge_request.create 

I have it under alias `gmr`, it will use default branch as a target

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#65

I tried this, and it seems very useful, but there's no documentation and the CLI help command doesn't work. Why make a tool and then not tell anyone how to use it? It's frustrating. No combination of `glab help command` or `glab command --help` works.

If you want a CLI tool for Gitlab, the tool called 'lab' has existed for years and _does_ have full featured help commands, as well as a ton of other features (like live views of CI jobs in your terminal). I recommend 'lab' very highly!

https://github.com/zaquestion/lab

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#66

I tried this, and it seems very useful, but there's no documentation and the CLI help command doesn't work. Why make a tool and then not tell anyone how to use it? It's frustrating. No combination of `glab help command` or `glab command --help` works.

If you want a CLI tool for Gitlab, the tool called 'lab' has existed for years and _does_ have full featured help commands, as well as a ton of other features (like live views of CI jobs in your terminal). I recommend 'lab' very highly! https://github.com/zaquestion/lab

I downloaded it earlier, it's great! I'm going to use that, thanks.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#67
post #62

As a GitLab team membmer, this is really awesome to see! A GitLab CLI is something I'd love to have officially at GitLab. Feel free to contribute to the discussion and help up vote the idea here https://gitlab.com/groups/gitlab-org/-/epics/3324

Alternate perspective: your trying to assess demand for a feature you’re curious about building, but the community already spoke. That’s a much stronger signal than people responding to your feature-vote thread.

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#68

Hosted on github. Ah the irony. Feels like a missed opportunity. On another note no have been using the GitHub cli client and it is great to be able to quickly create a PR from where I did the last push.

lol I was thinking exactly this

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#69

Earlier quoted context omitted.

I suspect due to the sheer number of internal deploys, Gitlab does not always get the exposure warranted. My work place is switching from internal Gitlab/gitlab-runners to external gitlab.com + internal gitlab-runners. We are very happy with both scenarios, but neither gains Gitlab any exposure.

you can create a merge request as well using only git, gitlab support it git push -o merge_request.create I have it under alias `gmr`, it will use default branch as a target

And the infinitely handy "push -o ci.variable=ALPHA=BETA" or its friend "push -o ci.skip" to influence the CI job that's created, if any, due to the push

https://docs.gitlab.com/ee/user/project/push_options.html#pu...

Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool

#70
post #46

Is there something similar out there for interacting with jira issues on the command line?

go-jira [1] is quite useful for avoiding Atlassian's UI. [1]: https://github.com/go-jira/jira

Also installable via "brew install go-jira"
Post reply on HN