There is also just "lab"[1]. [1] https://github.com/zaquestion/lab
Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
31–40 of 76 posts
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#32Hosted 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.
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.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#33Hosted 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 maintain a bunch of docker images that are purposed to run on gitlab ci, they are obviously hosted on github because only github has push-event integrations with docker hub. I make a push, docker hub builds and publishes the image, the image is only pulled by gitlab ci. Gitlab is great, but it lacks many popular integrations that must come from not-gitlab.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#34For anyone interested, there‘s a similar CLI for GitHub: https://github.com/cli/cli
Actually it's quite a shame for the Gitlab team that they don't offer a similar official CLI. The gitlab software is high quality in general, and obviously it's doable by a third party to implement such a tool.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#35Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#36My 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.
Disabling automatic repository housekeeping might help. It can use lots of RAM for large repositories like the Linux kernel.
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#37Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#38Earlier quoted context omitted.
I have created a small tool that automatically mirrors public repos from GitLab to GitHub: https://github.com/grdl/gitlab-mirror-maker Meaning, a repo can be hosted on GL but still benefit from better exposure and disoverability of GH.
But GitLab already has repo mirroring built-in, what am I missing?
Re: Take Gitlab to the command line with GLab, an open-source Gitlab CLI tool
#39Hosted 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 maintain a bunch of docker images that are purposed to run on gitlab ci, they are obviously hosted on github because only github has push-event integrations with docker hub. I make a push, docker hub builds and publishes the image, the image is only pulled by gitlab ci. Gitlab is great, but it lacks many popular integrations that must come from not-gitlab.