<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Playwright on Nick Liu - Software Engineer</title><link>https://nick-liu.com/tags/playwright/</link><description>Recent content in Playwright on Nick Liu - Software Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>nickboy@users.noreply.github.com (Nick Liu)</managingEditor><webMaster>nickboy@users.noreply.github.com (Nick Liu)</webMaster><copyright>2026 Nick Liu</copyright><lastBuildDate>Sat, 11 Jul 2026 15:08:00 -0700</lastBuildDate><atom:link href="https://nick-liu.com/tags/playwright/index.xml" rel="self" type="application/rss+xml"/><item><title>A typo fix shouldn't boot a browser in CI. Mine did for months.</title><link>https://nick-liu.com/posts/content-pr-ci-path-filter/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><author>nickboy@users.noreply.github.com (Nick Liu)</author><guid>https://nick-liu.com/posts/content-pr-ci-path-filter/</guid><description>&lt;div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"&gt;
 
I changed one sentence in a blog post, opened a pull request, and watched CI spend about 85 seconds installing a headless Chromium to confirm my prose still turned into HTML. The obvious fix, telling the workflow to ignore content paths, would have quietly broken every merge instead.

&lt;/div&gt;


&lt;h2 class="relative group"&gt;Symptom: a browser for a one-line edit
 &lt;div id="symptom-a-browser-for-a-one-line-edit" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#symptom-a-browser-for-a-one-line-edit" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Every pull request on this blog runs two jobs: a &lt;code&gt;lint&lt;/code&gt; job, and a
&lt;code&gt;build-and-test&lt;/code&gt; job. The second one builds the site with Hugo, link-checks the
output with htmltest, then installs a headless Chromium and runs a Playwright
suite against a live &lt;code&gt;hugo server&lt;/code&gt;. End to end, roughly 85 seconds, and almost
all of it is Playwright.&lt;/p&gt;</description></item></channel></rss>