<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Merge Request on Romano Roth</title><link>https://romanoroth.com/en/tags/merge-request/</link><description>Recent content in Merge Request on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Wed, 02 Nov 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/merge-request/index.xml" rel="self" type="application/rss+xml"/><item><title>GitLab DevSecOps Part 10: How to Do a Merge Request the Right Way</title><link>https://romanoroth.com/en/blogs/gitlab-devsecops-merge-request/</link><pubDate>Wed, 02 Nov 2022 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/gitlab-devsecops-merge-request/</guid><description>&lt;p>In the previous nine sessions Patrick Steger and I built a GitLab DevSecOps pipeline that runs SAST, secret detection, software composition analysis, container scanning and DAST. Useful — but only if it actually catches issues &lt;em>before&lt;/em> they reach the default branch. In Part 10 we close that loop: we wire the pipeline into Merge Requests so every change is scanned, the deltas against the default branch are visible, and approvals are required when new high or critical vulnerabilities appear.&lt;/p></description></item></channel></rss>