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.
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.
Meaning, a repo can be hosted on GL but still benefit from better exposure and disoverability of GH.
[1]: https://docs.gitlab.com/13.2/ee/user/project/repository/repo...
> git remote set-url --add --push origin <github-remote>
> git remote set-url --add --push origin <gitlab-remote>
This way I have an automatic backup to the second remote.
https://jigarius.com/blog/multiple-git-remote-repositories#t...
However, you can add multiple URLs to 'origin' and push to them all at once.
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.
git push -o merge_request.create
I have it under alias `gmr`, it will use default branch as a targethttps://docs.gitlab.com/ee/user/project/push_options.html#pu...
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
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.
1. I need to run gitlab ci myself on my host(s)
2. My host must be logged in to docker hub
3. Gitlab CI must run as privileged container
4. There are more hacks required to let gitlabci build the image and push as me.
on github you just authorize docker-hub to get webhooks from github, and that's it, it does the rest itself.
If making someone create a new account on Gitlab means they won't contribute to a project, then I'd rather publish it on GitHub instead, even if GitHub is closed-source. The network of GitHub is intrinsic to that website and Gitlab might not ever be able to replicate the size of its userbase. (Of course, if I'm proven wrong I'd migrate.)
Yes, it doesn't help Gitlab to have this mentality, but out of the dozens of OSS repositories I've used only two have come from Gitlab. Every single other one I had originally found on GitHub.