<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pull Request on Romano Roth</title><link>https://romanoroth.com/en/tags/pull-request/</link><description>Recent content in Pull Request on Romano Roth</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Romano Roth</copyright><lastBuildDate>Tue, 30 May 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://romanoroth.com/en/tags/pull-request/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub DevSecOps Part 10: Branch Protection and Pull Requests</title><link>https://romanoroth.com/en/blogs/github-devsecops-pull-request/</link><pubDate>Tue, 30 May 2023 00:00:00 +0000</pubDate><guid>https://romanoroth.com/en/blogs/github-devsecops-pull-request/</guid><description>&lt;p>In the previous nine sessions Patrick Steger and I built a GitHub DevSecOps pipeline with build, SCA, License Compliance, SAST, Container Scanning, Secret Detection and DAST. All useful — but only if it actually runs &lt;em>before&lt;/em> code lands in main, and only if the merge is blocked when something serious shows up. In Part 10 we wire that gate together with Pull Requests and Branch Protection rules.&lt;/p></description></item></channel></rss>