GitLab Duo Chat released as part of GitLab 16.11

GitLab has introduced that its AI assistant GitLab Duo Chat is now usually out there as a part of the GitLab 16.11 launch. 

GitLab Duo Chat can reply questions on points, epics, code, errors, CI/CD configurations, or the GitLab platform itself. It could additionally refactor present code and generate checks.

As an illustration, a developer onboarding onto a mission may ask for basic information like understanding the CI/CD setup, studying the distinction between a problem and an epic, resetting their GitLab password, and getting began with particular improvement frameworks. 

“With Chat, you’ve an assistant able to reply all your onboarding questions, and shortly you’re able to dig into your first mission,” GitLab wrote in a weblog submit. 

Organizations can management which knowledge the AI will get learn entry to on the mission, sub-group, and group ranges. GitLab additionally mentioned that buyer knowledge isn’t used to coach its AI fashions. 

GitLab Duo Chat is on the market inside GitLab and in fashionable IDEs like VS Code and JetBrains’ IDEs. It’s provided as an add-on to GitLab Duo Professional, which prices $19/consumer/month.

“Whether or not you’re a developer otherwise you’re managing your entire workforce, GitLab Duo Chat can empower you to make the most of AI precisely the place you want it all through the software program improvement lifecycle — all whereas serving to you keep code high quality and safety guardrails,” the corporate wrote. 

Different new options in GitLab 16.11 embrace:

• Coverage scoping, which permits compliance groups to set coverage enforcement to a selected group of tasks 
• Product Analytics, together with key utilization and adoption knowledge on customers
• The flexibility for Enterprise Customers to disable private entry tokens
• Autocompletion when inserting hyperlinks to wiki pages
• A sidebar containing mission info

In complete, over 40 new options have been added to GitLab 16.11. A full listing of updates might be present in GitLab’s weblog submit right here.