<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ci-Cd on Adur</title>
    <link>https://adurr.gitlab.io/tags/ci-cd/</link>
    <description>Recent content in Ci-Cd on Adur</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>&lt;a href=&#34;https://creativecommons.org/licenses/by-nc/4.0/&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;CC BY-NC 4.0&lt;/a&gt;</copyright>
    <lastBuildDate>Wed, 27 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://adurr.gitlab.io/tags/ci-cd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure Pipeline Template</title>
      <link>https://adurr.gitlab.io/projects/secure-pipeline-template/</link>
      <pubDate>Wed, 27 May 2026 00:00:00 +0000</pubDate>
      <guid>https://adurr.gitlab.io/projects/secure-pipeline-template/</guid>
      <description>&lt;p&gt;&lt;strong&gt;&amp;ldquo;Six Gates to Production&amp;rdquo;&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Most CI/CD templates stop at build-and-deploy. This one treats every commit as untrusted until six independent security tools have examined it. It is the pipeline I wish every client already had.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-problem-this-solves&#34;&gt;What problem this solves&lt;/h2&gt;&#xA;&lt;p&gt;A container image landing in production without being scanned is a liability. But bolting a scanner onto an existing pipeline is fragile: the scanner runs, the output gets ignored, and the deployment continues anyway. This template makes security gates non-negotiable. A critical finding in Semgrep, Trivy, or any other tool blocks the pipeline. A warning gets logged to a SARIF report. The deployment only proceeds when every gate passes.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PR Insights Action</title>
      <link>https://adurr.gitlab.io/projects/pr-insights-action/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://adurr.gitlab.io/projects/pr-insights-action/</guid>
      <description>&lt;p&gt;&lt;strong&gt;&amp;ldquo;A GitHub Action That Reads Your Pull Requests&amp;rdquo;&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Reviewing a large pull request often means scrolling through the diff to understand its scope. How many files changed? Which files were added versus modified? How many commits are in this branch? This action answers those questions automatically and posts them as a comment on the PR.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-it-does&#34;&gt;What it does&lt;/h2&gt;&#xA;&lt;p&gt;When a pull request is opened or updated, the action fetches PR data from the GitHub API and generates:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
