GitLab team member here. We published a blog post[0] yesterday that provides an overview of some features you may be interested in: Code Suggestions, Summarize MR Changes, Summarize My MR Review, and Explain this Code. You can find more information about these features via the links from the blog.
One thing I will say is that I notice lately that GitLab seems to throw in the word DevSecOps everywhere these days almost as if an exec has ordered everyone to use it a minimum of 20 times a day. It feels like the marketing people are pushing some kind of buzzword quota.
Nonetheless, will keep an eye on these features before our renewal cycle in September.
There's this rule - it likely has a name, but I don't know what it is - the rule saying that two-syllable names are by far the easiest, most effortless and most likeable ones to deal with (and any popular name that isn't two-syllable will eventually get a diminutive that is).
DevOps is two-syllable, so it stuck. DevSecOps is three-syllable, so it sucks. That's on top of it looking like it was created by means of someone saying "oh oh and also security, and also security!".
> Ironically, CI/CD and issues being well integrated were the reasons we switched to GitLab in the first place. But since then we stopped using issues.
Hah, yes. Do you have any idea how jarring it is to cheer for migrating issues from gitlab to jira? But it turns out that ugly but feature complete is better than easy to work with and missing key features (ever tried searching for something in issue comments? To say nothing of high level task tracking (management wants to know what blockers we have in this multi-step 23-item epic)).
