| GitLab 16.5 Adds Compliance Reports |
| Written by Kay Ewbank |
| Thursday, 26 October 2023 |
|
GitLab 16.5 has been released with compliance standards adherence reports and merge request target branch rules. GitLab, the web-based repository manager for Git GitLab specializes in providing a centralized, integrated platform for web developers with extensive features.
The first improvement to the updated version is a new tab on the Compliance Center for the standards adherence report. This report initially includes a GitLab best practices standard, showing when the projects in your group are not meeting the requirements for the checks included in the standard. Three checks are shown initially for approval rules that haven't been met. The three initial checks show unmet requirements for at least two approvers; the MR author is disallowed from merging; or committers to the MR are disallowed from merging.
The report contains details on the status of each check on a per project basis. It will also show you when the check was last run, which standard the check applies to, and how to fix any failures or problems that might be shown on the report. The developers plan to add more checks and expand the scope to include more regulations and standards. The second improvement is the inclusion of merge request target branch rules. These are aimed at projects that use multiple long-term branches for development, but want to keep main as the default branch. Target branch rules help ensure merge requests target the appropriate branch for your project and development workflow. Resolvable issue threads are the next addition. These are aimed at projects with long-running issues with many threads where it can be difficult to track what's going on. The addition means developers can now resolve a thread on an issue when the topic of discussion has concluded. The final main change is support for semi-linear fast-forward merge trains. Fast-forward merge trains were added to the previous release. Fast-forward merge is a merge method that avoids merge commits, while merge trains make it easier to merge into the main branch. The previous release enabled the two techniques to be used together. The latest change adds support for semi-linear merge methods. Now, if you want to ensure your semi-linear commit history is maintained you can use semi-linear fast-forward merge trains. GitLab 16.5 is available now.
More InformationRelated ArticlesGitLab 14.6 Adds Seamless Geo Experience GitLab 14.3 Adds Security Scan Policies GitLab 14 Offers DIY DevOps Alternative To be informed about new articles on I Programmer, sign up for our weekly newsletter, subscribe to the RSS feed and follow us on Facebook or Linkedin. 
Comments
or email your comment to: comments@i-programmer.info |
| Last Updated ( Thursday, 26 October 2023 ) |
