<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/a1848256318c4b92aefa965402c9dca9&quot; frameborder=&quot;0&quot; width=&quot;1664&quot; height=&quot;1248&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1248</height><width>1664</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1248</thumbnail_height><thumbnail_width>1664</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/a1848256318c4b92aefa965402c9dca9-00001.gif</thumbnail_url><duration>348.7000000000005</duration><title>Introducing the Ability to Use Templates from Different Branches 🎉</title><description> Hey team, I&apos;m excited to announce a new feature that allows us to use templates from different branches in our pipelines. Previously, we were limited to using the default branch&apos;s template, but now we have the flexibility to choose templates from any branch. In this video, I&apos;ll walk you through how to configure this feature and demonstrate how to use a template from a different branch in a pipeline. This update gives us the freedom to test changes and manage template versions more effectively. Take a look and start leveraging this powerful capability in our pipeline workflows. No action required, just watch and learn!</description></oembed>