GitLab 16.5 was introduced with updates to the Compliance Middle, merge request goal department guidelines, resolvable situation threads, and extra.
A brand new tab for requirements adherence stories was added within the Compliance Middle. These stories present which initiatives in a bunch don’t meet the verify for GitLab’s finest practices. These embody approval guidelines that require not less than approvers for merge requests (MRs), disallow the MR creator to merge, and disallow committers to merge.
Along with displaying particulars on every of these checks, the report additionally consists of info on when the verify was run, which normal the verify applies to, and repair issues that present up on the report.
The corporate plans to replace this reporting function sooner or later to incorporate checks on extra rules and requirements, and enhance how the report might be grouped and filtered.
A second main replace in GitLab 16.5 is that builders can now set goal branches for MRs, which may help make sure that the MR is focusing on the correct department for a specific challenge or improvement workflow. If no department is specified, it’ll use the default department of the challenge to focus on.
One other new function on this launch is the power to fast-forward merge trains which have a semi-linear historical past. This builds on the GitLab 16.4 replace, which first launched the power to fast-forward merge trains. “You may get all the advantages of merge trains, which guarantee all of your commits work collectively earlier than merging, with the cleaner commit historical past of quick ahead merges!” Grant Hickman, senior product supervisor at GitLab, wrote in a weblog put up saying the 16.4 updates.
Different new options embody the power to resolve a thread when a dialogue subject is closed, a extra outstanding button for altering between initiatives, and reviewer info for merge requests now seems within the Jira improvement panel.
Extra info on this launch is offered right here.