Great to see GitLab gain momentum in FOSS. It's a great fit for small teams too, it's easy to setup and keep updated. It's more important than ever to help GitLab gain adoption with GitHub making it free for private repos. I love GitHub as much as any developer, but I believe having a free, open alternative to it is important. I wish GitLab would improve their free-version of Merge Request reviews though, Github's is…
I'd love to hear more about what you dislike about merge request reviews. At work we've been talking about migrating looking for alternatives to GitHub over dissatisfaction with its code review interface, and, of course, GitLab is on the list of ones to check out.
Xfce switches to GitLab
51–60 of 148 posts
Re: Xfce switches to GitLab
#52Earlier quoted context omitted.
One thing I find annoying and occasionally hazardous about Gitlab merge requests is that per-file diffs which exceed a certain length are collapsed by default. This introduces risk since it is very easy for a reviewer to skim right past the collapsed file name, since one's eye tends to be drawn to the more salient red/green diff.
GitHub does this too, and it's awful. Why would anyone want to skip reviewing the biggest changes?
Though it can certainly hide much more relevant-to-reviewers changes easily.
Re: Xfce switches to GitLab
#53Earlier quoted context omitted.
I'd love to hear more about what you dislike about merge request reviews. At work we've been talking about migrating looking for alternatives to GitHub over dissatisfaction with its code review interface, and, of course, GitLab is on the list of ones to check out.
Code search, Gitlab doesn't have a code search feature. Paraphrasing The code search functionality can be achieved by adding Elasticsearch. We haven't added elasticsearch yet so cannot comment on the experience of using it.
Re: Xfce switches to GitLab
#54Re: Xfce switches to GitLab
#55Earlier quoted context omitted.
Does anyone else have things that make the switch from GitHub to GitLab a hard sell? I'm always curious why open source projects don't embrace an open platform, although I get that GitHub is fantastic in a lot of ways. I'm guilty of it myself, but I've reached the 50/50 GL/GH split as I try using GL more.
GL is not browsable with JavaScript disabled while GH is.
Re: Xfce switches to GitLab
#56Earlier quoted context omitted.
I'd love to hear more about what you dislike about merge request reviews. At work we've been talking about migrating looking for alternatives to GitHub over dissatisfaction with its code review interface, and, of course, GitLab is on the list of ones to check out.
Ability to review diff between two versions of PR is a great missing feature in GitHub. When dealing with large changes, GitLab review flow is IMHO easier for reviewer. Gitlab store each push of a MR branch as different version (as hidden refs), which make the feature possible. In GH, you force push a branch, you loose the old code for good, so reviewer has to remember why he did that comment before to see if it is s…
Re: Xfce switches to GitLab
#57Earlier quoted context omitted.
.
This past year, on my Thinkpad P50, I've switched between Ubuntu, Fedora, and Arch; Arch has by far been the least buggy. With Ubuntu, things would go haywire when docking/undocking. With Fedora, putting it to sleep was always a risk because after putting it to sleep I would sometimes I would open up my laptop to a black screen that I couldn't recover from. I was fine with that and just wouldn't put my laptop to slee…
Re: Xfce switches to GitLab
#58Would anyone doubt that open source contributions, and individual contributers even more so, have grown by an order of magnitude or more in the last decade or so? And that GitHub's process improvements and standardisation were the major factor in this?
It used to be, you had to mail patches to some mailing list, with each projects having their own set of arcane rules, sometimes written and sometimes informal, but always enforced with that very special enthusiasm stale organisations devote to policing arbitrary norms because that's the sole remaining source of the old timer's power differential.
Or at least that's how it seemed to me, for I never felt courageous enough to try.
These days, I fire off smaller contributions several times a week, and contribute some medium-sized feature once or twice a year.
Meanwhile, the most impressive thing about GitLab keeps being this strange quirk of them, that among all the companies I know, they are closest to being a total clone of an existing product. Or at least they were in the beginning, when their CSS still had ".gh-wide-3" class names.
Yet despite this, or maybe because of it, they are also the only company that repeatedly lorded it over their competitor when they came late to implementing some minor feature. Seriously: I noticed it the first time because it's a level of pettiness not usually seen. And since then, there have been three or four more instances.
Re: Xfce switches to GitLab
#59I find Gitlab UI quite a bit bloated and slow compared to Github. They have some amazing features but I can't get past how many (2-5 seconds) to load a page and sometimes upto 10 seconds (analytics). I hope that's being addressed in future. Usually, I spend at least 2 hours on Github in a given day - and probably access the website about 50 times a day or more. These UI issues add up tremendously.
Re: Xfce switches to GitLab
#60Earlier quoted context omitted.
I can confirm, this is the exact reason I made two copies of (shameless plug) the SpicaStack project earlier this month. GitHub's reach, network and stars help fellow devs and users discover our forks, while GitLab's exportability and amazing CI will let us actually work on it.
How do you keep the repos in sync?