On my quest for relentless optimization and efficiency, I came across new tools like gh or hub for GitHub that looked promising. Since we are mainly using GitLab, I decided to integrate glab which is a GitLab alternative of gh for a test.

I am especially interested in getting updates for Issues and the CI from the CLI.

CI

glab offers a nice overview of the pipeline triggered by your current commit. Just run glab ci view and you will receive something like:

╔════════════════════ Pipeline #20432 triggered about 2 days ago by Tobias Kriebisch ═════════════════════╗
║  ┌────────────────────┐           ┌────────────────────┐           ┌────────────────────┐               ║
║  │      Install       │           │        Lint        │           │        Test        │               ║
║  └────────────────────┘           └────────────────────┘           └────────────────────┘               ║
║                                                                                                         ║
║  ╔═════✔ composer═════╗           ┌──────✔ phpcs───────┐           ┌─────✘ phpunit──────┐               ║
║  ║                    ║           │                    │           │                    │               ║
║  ║             00m 37s║═══════════│             00m 09s│═══════════│             02m 22s│               ║
║  ╚════════════════════╝           └────────────────────┘           └────────────────────┘               ║

The view auto updates in real time. Very nice :).

If you have an error like in my example, you can get the output of the job with glab ci trace. It will ask for the specific job you want to read. Output has colors and looks like it was run in my own shell. Very pleasing for my eyes.

Issues

This is really awesome you can do almost everythin you can do from the web ui. Create issues (edit them with vim so cool), close, delete, list. It is pretty nice.

Conlusion

I will try to move everything I do with gitlab to the tool. Lets see how long this will work