<?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 Publishing House</title>
    <link>https://publishinghouse.org/tags/ci-cd/</link>
    <description>Recent content in ci cd on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/ci-cd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Deploying Hugo to Cloudflare Pages with GitHub Actions</title>
      <link>https://publishinghouse.org/deploying-hugo-to-cloudflare-pages-with-github-actions/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/deploying-hugo-to-cloudflare-pages-with-github-actions/</guid>
      <description>Cloudflare Pages is one of the best hosting targets for Hugo sites. It is fast, globally distributed, free for most publishing workloads, and integrates cleanly with GitHub repositories. You can deploy directly through Cloudflare&amp;rsquo;s built-in Git integration — or through a GitHub Actions workflow for more control over the build process. This guide covers both approaches and when to choose each.
Option 1: Cloudflare&amp;rsquo;s Direct Git Integration The simplest path requires no GitHub Actions configuration.</description>
    </item>
    
  </channel>
</rss>
