GitLab 16.5 was introduced with updates to the Compliance Middle, merge request goal department guidelines, resolvable subject threads, and extra.
A brand new tab for requirements adherence reviews was added within the Compliance Middle. These reviews present which tasks in a bunch don’t meet the verify for GitLab’s finest practices. These embrace approval guidelines that require at the very least approvers for merge requests (MRs), disallow the MR creator to merge, and disallow committers to merge.
Along with exhibiting particulars on every of these checks, the report additionally contains info on when the verify was run, which normal the verify applies to, and the best way to 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 will be grouped and filtered.
A second main replace in GitLab 16.5 is that builders can now set goal branches for MRs, which might help be certain that the MR is focusing on the correct department for a specific undertaking or improvement workflow. If no department is specified, it’ll use the default department of the undertaking 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 submit saying the 16.4 updates.
Different new options embrace the power to resolve a thread when a dialogue subject is closed, a extra distinguished button for altering between tasks, and reviewer info for merge requests now seems within the Jira improvement panel.
Extra info on this launch is out there right here.