<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Trigger on Personal Notes</title>
    <link>https://kewinremy.com/tags/trigger/</link>
    <description>Recent content in Trigger on Personal Notes</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 05 Jun 2026 07:08:52 +0200</lastBuildDate>
    <atom:link href="https://kewinremy.com/tags/trigger/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why GitLab&#39;s Run Pipeline UI Ignores Your Child Pipeline Variables</title>
      <link>https://kewinremy.com/notes/2026/05/why-gitlabs-run-pipeline-ui-ignores-your-child-pipeline-variables/</link>
      <pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate>
      <guid>https://kewinremy.com/notes/2026/05/why-gitlabs-run-pipeline-ui-ignores-your-child-pipeline-variables/</guid>
      <description>If you defined value/options/description on variables in a child pipeline file, GitLab&amp;#39;s Run new pipeline form won&amp;#39;t render them as dropdowns. Here&amp;#39;s why — and how to fix it.</description>
    </item>
  </channel>
</rss>
