I really like using Gitlab CI. We are building and deploying our applications using Gitlab CI mostly every day. It's very stable and fast. So that m overall experience is very good with Gitlab CI.

The working style of most of the CI/CD tools are similar in the background. The ones that has better UI and fast responses are making a difference in the market. Gitlab CI, by far has the best UI. The button clicks, flows and placement of the features are very well-designed.

I cannot say least but I would be happier if Gitlab adds more UI features in CI/CD level.

I think it's good that you can use it in basically the same way as GitHub, and that you can manage it by making use of your existing knowledge. Also, I think it's nice that GitLab has unique features that are easier to use, such as a feature that changes the display of the file icon for each file extension.

Using Git as a configuration management tool is already common sense (essential), but I think this software is the most used for remote (distributed) development. There are many cases where you install Git on each person's terminal and operate the commands, but if it is team development and you can't use an "external (public Internet) repository", it is better to set up and operate a Git repository with GitLab I think it will be the safest and standard way to use Git.

I guess there is no choice but to get used to it, but I would like to see more visual changes and expressions (messages) when conflicts occur that are easier to understand for beginners. After all, I'd like to see them develop an interface that makes it easier to understand the concept of Git configuration in the first place.

Not long ago, I ordered some GitLab licenses since more people wanted to use it. I asked to go from 57 to 75 licenses. Instead, GitLab put the order in wrong and added 75 licenses, bringing us to 132 total. About this time, I was pulled to a critically-important project that was way behind schedule and told not to work on anything else. When I got enough breathing room to switch back, [SENSITIVE CONTENT] acted like she couldn't care less. The most I ever got was "I'll be sure to look into it" or "I'm still looking into it". The process dragged on for weeks. I had to nag her over and over again for updates until she finally told me that GitLab's billing department had decided... not to give me a refund because it had been too long. How convenient, especially after dragging out the process for so long. I complained about this, asked for a new account manager, and got what I requested. [SENSITIVE CONTENT] took my concerns to the GitLab crew again... and got told once again that not only would we not receive a refund, GitLab wasn't going to offer us any sort of compensation or credit whatsoever. We're a software company as well, and we would never treat loyal customers this way - especially not our power users. I've built my DevOps career around GitLab and encouraged others to do the same. That GitLab could be so tone-deaf over a problem that was clearly their fault speaks volumes to how the company has changed.

GitLab does well as an all-in-one software development platform.

If GitLab makes a billing problem, it may refuse to rectify the problem as they did with us.

Its quite to easy to view stashed branch and some filter options in the repository. They can improve a bit to stay for the best in the market

At times , using the github & bitbucket in my project. This lags some feature which am seeing in the other repo cloud