229 karma · joined November 15, 2018
So disclaimer, I work for GitLab. But the draw to working here isn't the possibility of making an SF salary, it's to work remotely for the same salary as working for a local company. I don't really care if I'm making less than a colleague in SF, because the benefit of working remotely while not taking a pay cut is already worth it. It's not for everyone though, so if you don't see working from home as a big enough benefit then that's valid.
- The first iteration of Merge Trains [1] is released, allowing merges in the pipeline queue to run in parallel
- Merge requests for confidential issues [2]: there is now the ability to mark MRs on confidential issues as confidential, instead of having to work in a private repo
- Automated Let’s Encrypt certificates for GitLab Pages [3]
- Git object deduplication [4]
- Deploy Boards for Kubernetes clusters at the Group [5] and Instance [6] level
- Assigning groups as code owners [7]
[1] https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipeli...
[2] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...
[3] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...
[4] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...
[5] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...
[6] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...
[7] https://about.gitlab.com/2019/07/22/gitlab-12-1-released/?ut...
Hi! GitLab employee here. Mercurial support has been a hot-ish topic internally. If you want to weigh in then please comment on this Issue, since Issue interaction plays a big part of how we prioritize https://gitlab.com/gitlab-org/gitlab-ce/issues/31600
(edit: I'm an idiot I should've read the full thread first since someone already linked it. gonna leave it up anyway)
The goal is to go public by November 18, 2020. You can read all about it here: https://about.gitlab.com/company/strategy/
We have an MR open to mention our long term profitability target for Q4FY25 here: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/...
This does exist: https://docs.gitlab.com/ee/user/project/import/github.html#m...
Before I worked here, I was on a team that evaluated different devops tools, and I felt the same apprehension about the uptime. But we eventually chose gitlab, and the only real downtime we experienced was during the 2017 outage. And we liked having the option to switch to self-hosted if it became too much of an issue
> Putting aside valid thing that article was written by person with role at gitlab 'Content Marketer'
A lot of us in marketing have technical backgrounds and are GitLab code contributors, that's what made us competitive for the positions we were hired for. We just write a lot of the blog posts so the product teams can focus on their own work. They're also usually very collaborative.
Sorry if you meant no offense, it's just a bit of a button-press issue for me!