canvas VS glab

I usually have my main function be very scriptlike, with all the setup code, env vars and such in the beginning, and then starting whatever needs to be started. I think that's fine. See an example from some of my code here: https://github.com/golangdk/canvas/blob/newsletter-email/cmd/server/main.go

I don't know if you know about the history of the cli. For years it was looking like a hobby project from ProfClems https://github.com/profclems/glab and then it was adopted by Gitlab as their official CLI.

it's not official, but I like https://github.com/profclems/glab

#1: GitLab offering free certification for a short time | 19 comments #2: renew-le-certs | 0 comments #3: GLab v1.13.0 released: glab is an open-source GitLab command-line tool bringing GitLab concepts to your terminal next to where you are already working with Git and your code | 6 comments

For GitLab users, there is a project trying to give the same UX and functionality: https://github.com/profclems/glab

glab is able to do this

If ${repo} starts with gitlab, then use glab to clone the repo

Take a look at https://github.com/profclems/glab.

The `glab auth login` flow now includes a step to authenticate git as well when "HTTPS" is selected as the default git protocol. This enables git operations like clone, push, etc to automatically work with GitLab on a spotless system after the user has authenticated to `glab`

Check out the new features available in [v1.17.0](https://github.com/profclems/glab/releases/tag/v1.17.0)