Скачать или смотреть GitLab 17.8 - Support multiple distinct approval actions in merge request approval policies

You can create up to five approval rules for each merge request approval policy, allowing for more flexible and robust approval policies. Each rule can specify different approvers or roles and each rule is evaluated independently.

For example, security teams can define complex approval workflows such as requiring one approver from Group A and one from Group B, or one from a specific role and another from a specified group, ensuring compliance and enhanced control in sensitive workflows.

Previously, merge request approval policies supported only a single approval rule per policy, allowing for one set of approvers stacked with an “OR” condition. As a result, it was more challenging to enforce layered security approvals from varied roles, individual approvers, or separate groups.

OUTLINE
0:00 - Introduction
0:22 - Example Usage of Approval Actions
1:12 - Creating a Merge Request Approval Policy
3:05 - Approvals in Action via Merge Request (MR)
3:30 - Conclusion

USEFUL LINKS
Documentation: https://docs.gitlab.com/ee/user/appli...
Epic: https://gitlab.com/groups/gitlab-org/...
Release Post: https://about.gitlab.com/releases/202...

Thanks for watching! Be sure to subscribe and follow @awkwardferny and @gitlab on X (formerly twitter) and LinkedIn for similar content.