Over the past 6 months, there has been a significant increase in the error rates and substantial reduction in the reliability of GitLab. When GitLab was first launched I was one of the early adopters and champions. I even had a call once with your Chief Product Officer to discuss how things could be improved. A critical feature for adoption at organizations I have worked at was implemented which I was very grateful for. Now I am asking the Gitlab engineering team again for something critical to not only the future of software development at large but also my current team's and GitLab as a company's ultimate success. Please slow down. AI gives you the ability to make a lot of changes very fast. And at first glance it always looks right. But its not right. You know, you create these incidents: http://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22103 And then you lock the discussion? Why? Because every single developer who's day, week, demos and deliverable are affected by these frequent outages feels the same way. And you don't want anyone to know how frustrated we are with you. We trusted you when we decided to use GitLab, and that trust is rapidly eroding. My manager is already asking me about moving to other solutions like GitHub, but it seems they are making the same mistakes as GitLab, so I can't even recommend a decent alternative. At this point, we are seriously considering building our own alternative to GitLab. Even OpenAI has discovered the same problem with GitHub and GitLab. After all, anyone can do it now. Your community, good will, and trust is going to be the only real asset you have going into the future. Don't throw it away in the name of new features and trying to keep up with your competitors. Everyone hates this implosion of reliability. Not just developers. Set yourselves apart from the crowd. Deliver a product people trust when no one else is. -Josh