dsumenkovic

That's right, it's available in both free (SaaS) and core( self hosted) tiers.

Hello! Thanks for mentioning GitLab. I would like to ask if you could provide more details about what should be improved regarding the interface. Feel free to open an issue about it via https://gitlab.com/gitlab-org/gitlab-ce/issues.

We are heavily focusing on performance improvements - both in the product (so that features run better)[1] and in our GitLab.com infrastructure (so that GitLab.com runs more reliably)[2].

[1] - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?label...

[2] - https://gitlab.com/gitlab-com/infrastructure/issues

Overview of the three main improvements in this release: 1. Detect secrets and credentials in the repository

A recurring problem when developing applications is that developers may unintentionally commit secrets and credentials to their remote repositories. If other people have access to the source, or if the project is public, the sensitive information is then exposed and can be leveraged by malicious users to gain access to resources like deployment environments. GitLab 11.9 includes a new check called Secret Detection. It scans the content of the repository to find API keys and other information that should not be there. GitLab displays results in the SAST report in the merge request widget, pipelines reports, and the security dashboards.

2. Merge request approval rules

Code review is an essential practice of every successful project, but who should review the changes is not always clear. It is often desirable to have a variety of reviewers from different teams like Engineering, UX, and Product. Approval Rules allow you to better communicate who should participate in code reviews by specifying the eligible approvers and the minimum number of approvals for each. Approval rules are shown in the merge request widget so the next reviewer can quickly be assigned.

3. Move ChatOps to Core

Initially introduced in GitLab Ultimate 10.6, ChatOps has now moved to GitLab Core. GitLab ChatOps provides the ability to trigger GitLab CI jobs from Slack by using the slash commands feature. We are open sourcing this feature in alignment with our buyer-driven tier designation to encourage its use and contribution by the community.

That's so kind of you. I've reached out to you via community@gitlab.com. Thanks again!

Is the only option to add cities one-by-one via "edit company>cities>add city"? The list is a bit long, ~260 cities in total.

Hello, Community Advocate at GitLab here. Thanks for creating this base and adding us there.

GitLab is 100% remote company [1] with 500+ team members in 50+ accross the Globe [2].

Could you please also update this info at [3] since it states 11-50 employees. Almost forgot to mention that we have the team-pets page as well :)

[1] - https://about.gitlab.com/company/culture/all-remote/

[2] - https://about.gitlab.com/company/team/

[3] - https://remotehub.io/gitlab

This is great. Thanks for sharing!

Thanks for mentioning that. Here's some more info about it, an official doc https://docs.gitlab.com/ee/user/project/container_registry.h... and a blog post https://about.gitlab.com/2016/05/23/gitlab-container-registr....

This will be fixed in the release 11.9 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/25913

Thanks for the feedback. It's greatly appreciated.

Thank you very much for using GitLab. I wanted to share these details with you about the stability improvements https://about.gitlab.com/2018/10/11/gitlab-com-stability-pos....

GitLab Community Advocate here. Thank you very much for the feedback. I understand your desire to move some features to the lower tiers and that's a good sign for us that we are on the right path with our offerings. From time to time it happens that we move some features to the lower tiers or even core/free tier.

I wanted to share few more words on how we are trying to be the good stewards, you can find more about our stewardship rules and promises here https://about.gitlab.com/company/stewardship/#what-features-...

Here's a link to the self-hosted GitLab https://about.gitlab.com/pricing/#self-managed

Hello Max, Community Advocate at GitLab here.

Thank you for writing and sharing this interface with everyone. Could you please reach out to merch@gitlab.com, we'd love to share some gifts with you :-).

Here are more some details about that migration https://about.gitlab.com/2018/06/25/moving-to-gcp/ & https://about.gitlab.com/2018/07/19/gcp-move-update/.

Here are some more details about it https://about.gitlab.com/2016/04/07/gitlab-pages-setup/ and https://docs.gitlab.com/ee/user/project/pages/introduction.h...

Hello, Community Advocate at GitLab here. I am pleased to read your feedback about our product and values. Thank you very much for sharing your thoughts, we really appreciate that.

Totally understand your words about the credibility you've earned for your hard work during the past years, and we'd love to help you out with any concern or question you may have regarding the migration.

Here are some good overviews [1] & [2] which may give you a better picture of how the migration goes and how we could support your initiative.

[1] https://mail.haskell.org/pipermail/ghc-devs/2018-December/01...

[2] https://www.drupal.org/drupalorg/blog/developer-tools-initia...

Hello Tom, thanks for reaching out about this. I've forwarded your request to the team internally, please let us know when everything is sorted out :-).

Almost forgot to mention when you open the Contribute to GitLab link, under the Development section number 3. you can find out how to choose an issue that's most suitable to you.

Hi, I think these are the questions we all asked at a certain moment and everyone's experience was probably similar but also very specific and different. I started contributing to GitLab [1] and it was probably the easiest thing to do since you can even fix the simple typos on the website, handbook, blogs and that's really appreciated.

Another cool thing for me was the fact that you can use GitLab to contribute to GitLab [2].

It would be best to pick the topic you are most comfortable with (e.g. frontend HTML/JS) and after you dive in you'll definitely discover many other interesting areas you want to learn about.

You should definitely check out https://about.gitlab.com/community/contribute/ for more info on how to get started with contributing to open source. Feel free to join the Gitter room [3] and leave your questions in the chat.

Small note: My contributions led me to a job at GitLab, all the effort was seen and acknowledged and that made me feel really amazing! :-)

[1] - https://about.gitlab.com/what-is-gitlab/

[2] - https://about.gitlab.com/2015/07/07/how-we-use-gitlab-to-bui...

[3] - https://gitter.im/gitlabhq/community.

Hey laurynas, we'd love to hear what features you are missing. Is there already a feature proposal? If not, feel free to raise one over at https://gitlab.com/gitlab-org/gitlab-ce/issues.

Is the issue number 56210? Here's the full link https://gitlab.com/gitlab-org/gitlab-ce/issues/56210

Hey, I wanted to express the same enthusiasm as sytse. Thank you very much, your words are amazing and we are really happy to read this great feedback. Shared it with others so they can enjoy as well :-)

Also wanted to share this feature we are currently working on, it allows you to remove unused tags from Container Registry, and we hope it will land with release 11.7 https://gitlab.com/gitlab-org/gitlab-ce/issues/55978

Thanks for sharing this detail with everyone.

Thanks for the praise, I've just left a comment about our team which loves to communitcate with everyone here. More details above or https://news.ycombinator.com/item?id=18855469

Hi, Community Advocate [1] at GitLab here. I am part of the team which takes care of our community and that includes the communication with users.

Briefly our (my team's) goal is to respond to every question about GitLab asked online and to stay transparent [2] about evrerything. This helps us to create better documentation and processes as well as it's easier to provide feedback into GitLab.

Regarding the user feedback and preferences on HN, everyone's comment is welcome and we really appreciate the words from the competitor's side.

It's really interesting that many people at GitLab joins the HN threads and you probably noticed our CEO's activity as well as many other GitLabbers.

[1] https://about.gitlab.com/job-families/marketing/community-ad... [2] https://about.gitlab.com/handbook/values/#transparency

Hey Vinay, there's also a notable difference, at GitLab you don't have a limit to 3 user per private project.

Hi Eduardo, thanks for writing about your experience with GitLab Issue Boards.

Could you please tell us what could make your experience more convenient? Do you have an open issue regarding your suggestions? If not, it would be great if you could open an issue about it at https://gitlab.com/gitlab-org/gitlab-ce/issues. We'd like to follow up on it.

It’s really valuable for us when users take the time to submit issues for bugs, changes, or feature proposals. This helps us steer the product in the right direction.

Hey, did you mean of assigning approvers based on code owners [1]? You can find more info about Code Owners and syntax at the documentation [2].

[1] https://gitlab.com/gitlab-org/gitlab-ee/issues/1012 [2] https://docs.gitlab.com/ee/user/project/code_owners.html

Thanks for sharing these tips with the community.