Live data from Hacker News

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

github.com

71–76 of 76 posts

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

#71

Earlier quoted context omitted.

it's a paid feature: not in community gitlab

If your project is open source on gitlab.com - you get all paid features for free.

Here is a link to our program for open source projects for anyone interested! https://about.gitlab.com/solutions/open-source/ (community advocate at GitLab)

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

#72
post #69

Earlier quoted context omitted.

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

That's the first I've read of `push -o`. Does GitHub have push options like that as well?

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

#73
post #72
post #69

Earlier quoted context omitted.

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

That's the first I've read of `push -o`. Does GitHub have push options like that as well?

That's the first I ever heard of it, either, and was unable to find out if those options are exposed more generally to the CI pipeline (so can I make my own "-o" toys?)

I don't recall ever hearing of any such thing in GitHub, and their help search is so atrocious I don't know that I'd be able to find the answer even now. That said, I can't imagine that kind of customization fits into GitHub's mental model, which goes double given that they just recently even _developed_ a CI system to which one could send those options

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

#74
post #31
post #26

There is also just "lab"[1]. [1] https://github.com/zaquestion/lab

lab is great! The CI view in the cli felt kind of magical at the time. I was in an organization that was bizarrely using both GitHub ant GitLab, and lab+hub really helped make sense of things until we finally migrated to GitLab. Using GitHub exclusively at the new job has me really missing GitLab CI when working the GitHub actions :(

The biggest missing feature in GitHub for me is "Merge when green". I wonder why they didn't add this yet.

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

#75

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 understand the irony but here's the case where most Gitlab users only have account with their company's self hosted gitlab platform and hence can't contribute to FOSS on Gitlab unless they create another account. I hosted it on Gitlab for OSS visibility and get more users contributing to the project.

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

#76

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.

This issue has been fixed!
Post reply on HN