153 engineers on Hacker News describe using GitLab first-hand: 50 endorse it, 18 regret it, 27 are mixed.
“We use GitLab where I work. The only problem is it calls pull requests "merge requests," and I don't think I'll ever get used to saying "MR"”
mixed · production · stack_framer · 2026-11-04 · source ↗ · wrong label?“the gitlab CI seems like a nice balance between powerful when it needs to be and simple otherwise for our use case so there is nothing driving us to swap.”
endorse · production · tempest_ · 2026-10-30 · source ↗ · wrong label?“4 years of running production GitLab on nightly is very impressive! ... Clearly the quality of GitLab releases is much higher than I imagined.”
endorse · production · 4 yr · Nemo_bis · 2026-08-18 · source ↗ · wrong label?“It was fast, self hosted, and full of features, especially useful around quality gates and build on PRs.”
endorse · production · spockz · 2026-01-24 · source ↗ · wrong label?“We switched to gitlab at work about five years ago... My least favorite feature is actually the sheer number of features.”
mixed · production · 5 yr · javier2 · 2026-01-24 · source ↗ · wrong label?“it took something like 32 gigs of ram on their MergeRequestProcessor SideKiq worker... I think all that work just let us continue to use GitLab”
mixed · production · doublet00th · 2025-12-31 · source ↗ · wrong label?“GitLab started choking on the size of our CI configuration and we'd see a spinner for about 5 minutes before our pipeline even launched.”
regret · production · doublet00th · 2025-12-30 · source ↗ · wrong label?“we rent 7*4$ VPS, install gitlab CI runners on them, saving us from hundreds $$$ per month and 45mins/merge”
endorse · production · inchidi · 2025-12-16 · source ↗ · wrong label?“A breath of fresh air after the unceasing misery and pain that is Gitlab and GHA.”
regret · production · regularmother · 2025-12-16 · source ↗ · wrong label?“we've run it on Kubernetes for 6 years. It's never gone down for us, maybe an hour of downtime yearly”
endorse · production · 6 yr · tapoxi · 2025-11-18 · source ↗ · wrong label?“after spending a few years with gitlab pipelines, my company started migrating over to dagger”
regret · production · 3 yr · rgilton · 2025-03-20 · source ↗ · wrong label?“Gitlab was a massive pain and became close to unusable on that same server before we migrated to gitea”
regret · production · homebrewer · 2025-03-18 · source ↗ · wrong label?“We migrated to GitLab with unanimous enthusiasm – so many new features, so many things worked better”
endorse · production · acdha · 2024-12-06 · source ↗ · wrong label?“Latency of Navigating Gitea is also instant by comparison to Gitlab which was driving us nuts it's so slow.”
regret · production · tomxor · 2024-11-17 · source ↗ · wrong label?“GitLab is fine-I-guess, we use it at work--but at home I use GitHub and self-hosted runners”
mixed · production · eropple · 2023-12-19 · source ↗ · wrong label?“We run a self-hosted Gitlab Premium instance installed with Omnibus for 30 devs and we actually install Gitlab updates on a cron.”
endorse · production · 5 yr · Xiol32 · 2023-12-17 · source ↗ · wrong label?“Gitlab is one of these exceptions but generally it's been working well for us.”
endorse · production · Foxboron · 2023-12-08 · source ↗ · wrong label?“Project Managers are missing some features, but the devs (including me) like it a lot more due to integrating so well with PRs/commits.”
mixed · production · preisschild · 2023-10-16 · source ↗ · wrong label?“At a previous company, we switched to Gitlab for the specific reason that they handled notebook diffs slightly better.”
endorse · production · skadamat · 2023-07-19 · source ↗ · wrong label?“Their pricing update end of last year was one of the reasons we switched over to Github.”
regret · production · derN3rd · 2023-06-20 · source ↗ · wrong label?“Do you have any idea how jarring it is to cheer for migrating issues from gitlab to jira?”
regret · production · yjftsjthsd-h · 2023-05-04 · source ↗ · wrong label?“CI/CD and issues being well integrated were the reasons we switched to GitLab in the first place.”
endorse · production · atonse · 2023-05-04 · source ↗ · wrong label?“for us, that means VSCode, DBeaver, and GitLab all work nicely”
endorse · production · rhco · 2023-03-27 · source ↗ · wrong label?“Over time we got tired of the maintenance and the system was just slowly coming to a crawl. We switched to GitHub”
regret · production · lazypenguin · 2023-03-02 · source ↗ · wrong label?“direct from the gitlab pipeline.. not sure how can it be easier than that.”
endorse · production · pelasaco · 2023-01-26 · source ↗ · wrong label?“we switched to our own hosted-on-k8s GitLab summer 2019 and it's been rock solid since. I patch it monthly (via Helm) and it's painless.”
endorse · production · 3 yr · tapoxi · 2022-12-21 · source ↗ · wrong label?“Used to use Gitlab runners, Bitrise, Github Actions, etc. They're all too slow, because all these services make money”
regret · production · ohgodplsno · 2022-12-09 · source ↗ · wrong label?“my large enterprise employer licenses GitLab Premium and it's worth every cent we pay”
endorse · production · dekhn · 2022-11-24 · source ↗ · wrong label?“they failed to fix it so now we run on the community edition which just works.”
mixed · production · jeltz · 2022-11-02 · source ↗ · wrong label?“no downtime that wasn't planned when we self-hosted. Load was very predictable, and ran on k8s anyway. Much, much faster than the hosted version.”
endorse · production · qeternity · 2022-04-14 · source ↗ · wrong label?“Loved it for the 3 1/2 years I was a user.”
endorse · production · 3.5 yr · Beltiras · 2022-03-24 · source ↗ · wrong label?“It's good for my small team, we moved off Trello to that. Issues list and a simple board for visualization”
endorse · production · edoceo · 2022-01-07 · source ↗ · wrong label?“which was comparably better... but I still get lost in gitlabs interface when compared with github”
mixed · production · tomxor · 2021-11-17 · source ↗ · wrong label?“GitLab has been great for us so far.”
endorse · production · danudey · 2021-09-17 · source ↗ · wrong label?“Our entire company was on Gitlab.com for 4 years without paying a single dime to them... I loved how simple everything worked. Their CI is top-notch.”
endorse · production · 4 yr · rhacker · 2021-09-17 · source ↗ · wrong label?“We run a stupidly simple (though small scale) gitlab instance in docker”
endorse · production · martingab · 2021-08-03 · source ↗ · wrong label?“We switched from self-hosted to gitlab.com a couple months back and the migration has been extremely disappointing.”
regret · production · qeternity · 2021-03-15 · source ↗ · wrong label?“Self hosted gitlab is nice, until you realize that you can get the same functionality for free from Github... we got a little worried about our flaky backups... we switched to Github.”
mixed · production · jillesvangurp · 2021-02-10 · source ↗ · wrong label?“I managed to convince the team about Gitlab and we migrated, initially in the Free tier. My first surprise was that Gitlab does not allow for Monthly payments”
mixed · production · xtracto · 2021-01-26 · source ↗ · wrong label?“in the 2-3 years of running a Gitlab instance, which has 1300 users, I only had 2-3 incidents”
endorse · production · 2.5 yr · mgbmtl · 2020-10-28 · source ↗ · wrong label?“We migrated to on-prem GitLab running on k8s via the official Helm chart a year ago... I don't regret it.”
endorse · production · 1 yr · tapoxi · 2020-07-15 · source ↗ · wrong label?“We run a medium sized Gitlab instance... Gitlab is actively hostile to you building automations on top of it.”
mixed · production · orf · 2020-06-12 · source ↗ · wrong label?“We switched last year and it keeps paying dividends for our security programs. I hope they begin to focus on more production stability, this week alone we've had 3 disruptions”
mixed · production · 1 yr · bearjaws · 2020-05-22 · source ↗ · wrong label?“deployments through Gitlab environments are a big improvement over our Jenkins deployment job, so we still ship as often as we want.”
endorse · production · harrisonjackson · 2020-04-16 · source ↗ · wrong label?“We use GitLab at work and I use it for personal projects as well, it has been very slow for several days now... I love the platform in general”
mixed · production · Uninen · 2019-11-28 · source ↗ · wrong label?“We use Gitlab at the office and it is constantly slow. Might be our setup I agree, but in the end it also tarnishes the brand to me.”
regret · production · jlengrand · 2019-11-28 · source ↗ · wrong label?“We run our own instances and would be fine even if a FAANG bought it and killed it.”
endorse · production · bsder · 2019-09-30 · source ↗ · wrong label?“I am a huge fan of gitlab. We are in the process of moving our github org over. We love!! the gitlab ci tools.”
endorse · production · timwayne16 · 2019-09-17 · source ↗ · wrong label?“"Service Desk" became a killer feature. That lets users file issues directly into our GitLab issue tracker by sending an email”
endorse · production · sstangl · 2019-09-17 · source ↗ · wrong label?“We love!! the gitlab ci tools. We use them extensively for mobile cicd. ... My only nitpick is the regex matching”
mixed · production · harrisonjackson · 2019-09-17 · source ↗ · wrong label?“they take a massive premium if you're not interested in the other features. Still, the basics are sound”
mixed · production · Spidler · 2019-08-27 · source ↗ · wrong label?“We run Gitlab on premise during last 4 years and I can't complain on those costs - updates are "click this button"”
endorse · production · 4 yr · majkinetor · 2019-08-09 · source ↗ · wrong label?“After using it for our test pipelines for a year we've switched to GitLab CI completely with our deployments”
mixed · production · 1 yr · Roritharr · 2019-01-22 · source ↗ · wrong label?“We use gitlab and have always treated gitlab as a first class citizen.”
endorse · production · duncan-donuts · 2018-12-14 · source ↗ · wrong label?“At my previous job we switched to GitLab during the period where GitHub felt like it wasn't improving... we definitely used GitLab CI and registry”
endorse · production · jchw · 2018-11-13 · source ↗ · wrong label?“I absolutely want 3 hosts for less then 100$, a gitlab account for 4$, a free account in cloudflare”
endorse · personal · mcs_ · 2018-10-04 · source ↗ · wrong label?“At my place we moved to GitLab 2.5 years ago... it's just getting worse update after update.”
regret · production · 2.5 yr · cheghook · 2018-08-02 · source ↗ · wrong label?“We set up GitLab to help establish innersourcing... we'd have to pay $325.000 for the pleasure. And that is going nowhere.”
mixed · production · elygre · 2018-07-23 · source ↗ · wrong label?“Speed. Gitlab is so slow; it's actually one of the main reasons why we moved out of it.”
regret · production · maktouch · 2018-06-06 · source ↗ · wrong label?“We don't like GitLab as it was slow when we tested it and the UI wasn't designed as nicely as the other two”
regret · personal · foobarbazetc · 2018-06-05 · source ↗ · wrong label?“We're using gitlab and are quite happy with it.”
endorse · production · acomjean · 2018-06-04 · source ↗ · wrong label?“I first tried migrating to GitLab when the public cloud first came out and abandoned it due to performance. However, I re-valuated and did migrate about 2 years ago and it has been fine”
mixed · production · 2 yr · singlow · 2018-06-04 · source ↗ · wrong label?“We moved to GitLab (self hosted) and it's been nothing but incredibly reliable for our 120~ people organisation”
endorse · production · mrmondo · 2018-06-04 · source ↗ · wrong label?“I love gitlab. I have it running for a small team on a Digital Ocean Droplet it was trivial to get running.”
endorse · production · lttlrck · 2018-05-07 · source ↗ · wrong label?“We switched over to Gitlab from Stash about 9 months ago and it's been fantastic. ... the CI/CD integration has been smooth.”
endorse · production · 0.75 yr · tenaciousDaniel · 2018-04-23 · source ↗ · wrong label?“One of my repos has been stuck in limbo for over 2 months now after I attempted to migrate it to a group namespace from my own profile.”
mixed · personal · zaarn · 2017-11-15 · source ↗ · wrong label?“We switched a large Nodejs project from TFS to GitLab and it's been night-and-day on our productivity.”
endorse · production · 0xfeba · 2017-09-22 · source ↗ · wrong label?“In my organization we run a Gitlab instance with at least 20 active users (70 users total)... usually it runs quite fast.”
endorse · production · snorremd · 2017-07-07 · source ↗ · wrong label?“At work we switched to gitlab for new projects and loving.”
endorse · production · psankar · 2017-03-22 · source ↗ · wrong label?“it was a big mistake picking gitlab.com since we could be paying GitHub and be productive”
mixed · production · 0.5 yr · b0ti · 2017-02-01 · source ↗ · wrong label?“We've been using this for over a year without issues now.”
endorse · production · 1 yr · Cidan · 2016-12-23 · source ↗ · wrong label?“As a paying gitlab ee customer, we love to use gitlab.”
endorse · production · wernerb · 2016-12-22 · source ↗ · wrong label?“Sadly this does not fix bugs. And the issue tracker of gitlab-ce grows and grows and the CI is not really stable.”
mixed · production · merb · 2016-12-20 · source ↗ · wrong label?“Well we switched from Stash/BitBucket to it and are still happy since we screwed JIRA also and it's way easier to maintain.”
endorse · production · merb · 2016-11-23 · source ↗ · wrong label?“We run GitLab via the omnibus package in our data centre on a modest VM and it's no slouch”
endorse · production · petepete · 2016-10-22 · source ↗ · wrong label?“We moved to gitlab a couple of months ago (the public one) and it's really slow so we are thinking of having gitlab only for CI and do everything else on github.”
regret · production · Keats · 2016-09-13 · source ↗ · wrong label?“my god it's damn good, It's really impressed us particularly in the last 12 months”
endorse · production · mrmondo · 2016-08-05 · source ↗ · wrong label?“which is why we switched to a local instance of Gitlab: stuff still works, no matter whether Github is in business”
endorse · production · Piskvorrr · 2016-04-05 · source ↗ · wrong label?“I am using a gitlab instance for about 2 years on my personal server and have been very happy with it.”
endorse · personal · 2 yr · arlcode · 2015-07-09 · source ↗ · wrong label?“I really like Gitlab and have been using it for my projects but the lack of a notifications panel is annoying.”
mixed · personal · wldcordeiro · 2015-07-09 · source ↗ · wrong label?“Whilst there are good features that we like, it's so hard to navigate to where you want to be... I kind of regret it.”
mixed · production · 1 yr · jbrooksuk · 2015-07-09 · source ↗ · wrong label?“We use gitlab at PacketZoom too and are mostly happy with this. Issue management is probably the weakest part of gitlab”
mixed · production · chetanahuja · 2015-07-09 · source ↗ · wrong label?“I've been using Gitlab now for a few months and really like it but I've run into some bugs on gitlab.com”
mixed · personal · wldcordeiro · 2015-07-09 · source ↗ · wrong label?“We moved to Gogs. GitLab was too slow, and started giving us random 500 errors (fatal bug).”
regret · production · izolate · 2015-03-16 · source ↗ · wrong label?“Lots of features, and they are easy to use. Upgrading to the newest version has always been simple.”
endorse · production · hmottestad · 2015-03-16 · source ↗ · wrong label?“we installed an instance of GitLab. It is really awesome, a private GitHub for your needs. The setup was a pain though”
mixed · production · hypr_geek · 2014-04-22 · source ↗ · wrong label?“We switched from Gitlab to Stash few months ago. Mainly because Stash upgrade was way easier than Gitlab at that time.”
regret · production · linc01n · 2014-04-22 · source ↗ · wrong label?“We've had no issues with it and it's really been a great move for us.”
endorse · production · mrmondo · 2014-04-22 · source ↗ · wrong label?“I've been using GitLab since 4.0, but I've not got it completely updated because it's such a pain in the ass.”
mixed · personal · girvo · 2013-11-24 · source ↗ · wrong label?“Been using GitLab since (I think) 4.0 and have yet to experience any problems upgrading on a fairly standard ... setup on a VPS.”
endorse · personal · actionscripted · 2013-11-24 · source ↗ · wrong label?“gitlab definitely looks nicer, probably can do even more.. it has pull requests which are (yet) missing in gitblit.”
mixed · personal · buster · 2013-03-22 · source ↗ · wrong label?“We run GitLab.com with 3000+ users on a moderate (c1.medium, 1.7 GiB) instance. I think you will do fine with GitLab 5.0”
endorse · production · sytse · 2013-03-22 · source ↗ · wrong label?“It was the amount of system work required (sudo-ing, chmod-ing, installing mysql because we only used postgres before, creating users) that made me give up eventually.”
regret · personal · n0nick · 2012-12-23 · source ↗ · wrong label?“We've been using it a few months and really like it.”
endorse · production · contingencies · 2012-12-23 · source ↗ · wrong label?“we run it for our repos, plus you can be in control of number of repos allowed per user.”
endorse · production · ncavig · 2012-11-30 · source ↗ · wrong label?“We use gitlab and there's probably some way to hook up a custom external review tool easily”
neutral · production · stevenhuang · 2026-10-20 · source ↗ · wrong label?“We run our own gitlab instance in a central AWS account”
neutral · production · hangrybear666 · 2026-10-14 · source ↗ · wrong label?“So we had to migrate to GitLab.”
neutral · production · kgeist · 2026-10-06 · source ↗ · wrong label?“At some point our devops guy installed Gitlab around that, but we never really used the web ui.”
neutral · production · donatj · 2026-02-21 · source ↗ · wrong label?“It was hosting a lot of our software development apps like GitLab, Nexus, KeyCloak, etc”
neutral · production · firesteelrain · 2026-01-26 · source ↗ · wrong label?“all of our GitLab jobs are just one-line invocations of our wrapper scripts”
neutral · production · pxc · 2025-12-15 · source ↗ · wrong label?“we run a private gitlab instance and a merge request can spawn hundreds of jobs”
neutral · production · Cthulhu_ · 2025-12-08 · source ↗ · wrong label?“we run GitLab server and runners all on podman”
neutral · production · firesteelrain · 2025-09-05 · source ↗ · wrong label?“do the pip install stage in a 2CPU/4GB Gitlab runner”
neutral · production · alisonatwork · 2025-08-14 · source ↗ · wrong label?“We have something like ~40 repos in our private gitlab repo, and each one has its own CI system”
neutral · production · yc-kraln · 2025-05-28 · source ↗ · wrong label?“it lasted about a year before the popularity factor kicked in and we switched to GitLab.”
neutral · production · andrewaylett · 2025-05-02 · source ↗ · wrong label?“90% of comments in my team's PRs come with suggestions that can be applied with a click (we use GitLab).”
neutral · production · throw-qqqqq · 2024-12-27 · source ↗ · wrong label?“to self hosted Gitlab, eventually landing on just standard GitHub.”
neutral · production · donatj · 2024-09-29 · source ↗ · wrong label?“I've been using a similar HTML file (local at first, now hosted on GitLab)”
neutral · personal · psafronov · 2023-12-11 · source ↗ · wrong label?“We use GitLab at work, so I wouldn't be able to use it there”
neutral · production · mplanchard · 2023-12-05 · source ↗ · wrong label?“We've moved to plain markdown in Git(Lab) as Confluence replacement. A CI pipeline compiles it to HTML and hosts it on the web”
neutral · production · HHad3 · 2023-10-16 · source ↗ · wrong label?“On my workplace we use self-hosted GitLab and GitLab CI. The CI allows you to allocate dedicated server instances to specific CI tasks.”
neutral · production · GolDDranks · 2023-09-30 · source ↗ · wrong label?“aliases that connect to various (self-hosted) Gitlab projects for work, where we use service-desk”
neutral · production · mgbmtl · 2022-12-24 · source ↗ · wrong label?“You should be able to find the terraform and config for it all on our gitlab instance.”
neutral · production · scrollaway · 2022-12-22 · source ↗ · wrong label?“for project management Gitlab professional.”
neutral · production · InsOp · 2022-12-11 · source ↗ · wrong label?“needs to takes Jira issues as input and produce Gitlab merge requests as output”
neutral · production · ChuckNorris89 · 2022-11-21 · source ↗ · wrong label?“We've switched to GitLab, and while I can drag and drop the 50% smaller .mov”
neutral · production · duffyjp · 2022-11-14 · source ↗ · wrong label?“We activated Slack, Sentry and GitLab integrations too.”
neutral · production · new_here · 2022-06-30 · source ↗ · wrong label?“You deploy it using that directly from you gitlab/github. You copy paste your artifact and it's there.”
neutral · production · maxdo · 2021-12-16 · source ↗ · wrong label?“I've been using it for more than five years and if I had to use GitHub actions, I'd rather spend two hours getting to the bottom of it”
neutral · production · 5 yr · Jugurtha · 2021-12-11 · source ↗ · wrong label?“We run hurl tests on every branch of our projects, via Gitlab pipelines.”
neutral · production · jayteee · 2021-10-07 · source ↗ · wrong label?“At a previous place we migrated from Github to Gitlab, but we have to keep the GH repo for the merge request, approvals and paper trial.”
neutral · production · xtracto · 2021-07-06 · source ↗ · wrong label?“Our GitLab board looked like Backlog -> In Progress -> Review -> Done.”
neutral · production · jlund-molfese · 2021-04-20 · source ↗ · wrong label?“we ran into various limitations we ran into, my manager decided he "had a bad experience with Gitlab" and so we switched providers.”
neutral · production · zymhan · 2021-01-27 · source ↗ · wrong label?“we're using all the modern cloud tooling: Spring Boot, Azure, containers, K8S, Gitlab pipelines.”
neutral · production · twh270 · 2020-12-21 · source ↗ · wrong label?“When we migrated to GitLab, we used it to coordinate external dependencies between Docker->GitLab registries, using GitLab CI”
neutral · production · neomantra · 2020-11-03 · source ↗ · wrong label?“We switched to Gitlab at Arch Linux recently as well”
neutral · production · scrollaway · 2020-05-31 · source ↗ · wrong label?“at work when we moved to wfh we started using gitlabs time tracking features on all tickets.”
neutral · production · Polylactic_acid · 2020-05-29 · source ↗ · wrong label?“Boris was quite reliable, the only issues we had was when we occasionally ran out of disk space”
neutral · production · bottled_poe · 2020-05-28 · source ↗ · wrong label?“the only channel I'm connected to the company is the email and selfhosted gitlab.”
neutral · production · konart · 2020-05-23 · source ↗ · wrong label?“We run our own self-hosted GitLab EE instance, so we have "infinite" CI minutes in that the runners are on all our own hardware.”
neutral · production · umvi · 2019-09-17 · source ↗ · wrong label?“More anecdata: I run self-hosted GitLab, Nextcloud, and Wallabag.”
neutral · personal · katet · 2019-08-02 · source ↗ · wrong label?“GitLab (issues, CI build results), and social media (followers, mentions) are announced there”
neutral · production · NorthCon_de · 2019-06-08 · source ↗ · wrong label?“deploys from gitlab/bitbucket pipelines”
neutral · production · apeacox · 2018-12-23 · source ↗ · wrong label?“since we run GitLab already”
neutral · production · apple4ever · 2018-07-26 · source ↗ · wrong label?“When we switched from GitLab to GitHub Enterprise at work, our CI environment just needed to point somewhere else.”
neutral · production · favorited · 2018-01-03 · source ↗ · wrong label?“we use gitlab to render and deploy a template as a normal k8s object.”
neutral · production · xur17 · 2017-12-19 · source ↗ · wrong label?“GitLab will apply basic Org formatting (as with markdown), so I can share them directly just by pushing”
neutral · personal · gavinpc · 2017-11-24 · source ↗ · wrong label?“Right now: Self hosted Gitlab CE. Gitlab runners in pre-emptibles nodes with autoscaling”
neutral · production · maktouch · 2017-10-31 · source ↗ · wrong label?“The migration basically consisted of clicking the import button and making sure everybody's remotes were changed over.”
neutral · production · sevensor · 2017-10-16 · source ↗ · wrong label?“It integrates so well with our Gitlab/Jenkins flow, too.”
neutral · production · frikk · 2017-04-11 · source ↗ · wrong label?“I'm interested in exploring adding it as a feature of our GitLab.”
neutral · production · sytse · 2016-12-30 · source ↗ · wrong label?“We run gitlab and the full config is 57 lines. A little more than half of those are comments or blank lines.”
neutral · production · tomsthumb · 2016-12-23 · source ↗ · wrong label?“Same permission system as our code via MRs using Gitlab.”
neutral · production · stp-ip · 2016-12-12 · source ↗ · wrong label?“we run the official GitLab Docker image and it consists of many processes.”
neutral · production · profmonocle · 2016-10-24 · source ↗ · wrong label?“In fact our .gitlab-ci.yml looks very similar to the example under "elaborate example" in the blog post.”
neutral · production · mikewhy · 2016-05-23 · source ↗ · wrong label?“I personally also use Gitlab for private side project repos”
neutral · personal · alfg · 2016-05-11 · source ↗ · wrong label?“when the opportunity arose to switch to gitlab with no commit signing required whatsoever, we switched immediately.”
neutral · production · michaelt · 2016-04-05 · source ↗ · wrong label?“but we moved to git-shell right after that, and to gitlab not long after when then team grew beyond a handful of people.”
neutral · production · dvirsky · 2016-02-07 · source ↗ · wrong label?“I've been doing most of my scientific work in GitLab during that time”
neutral · personal · 2 yr · timtylin · 2015-03-15 · source ↗ · wrong label?“we migrated the company projects to GitLab as well.”
neutral · production · 1 yr · thecodemonkey · 2014-04-22 · source ↗ · wrong label?“I modified the introduction to make it clear we run on Gitlab in the first sentence.”
neutral · production · sytse · 2012-08-24 · source ↗ · wrong label?