<?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/058f59b6f899448e9de568d374e9bbeb&quot; frameborder=&quot;0&quot; width=&quot;3840&quot; height=&quot;2880&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2880</height><width>3840</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2880</thumbnail_height><thumbnail_width>3840</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/058f59b6f899448e9de568d374e9bbeb-985816908656de59.gif</thumbnail_url><duration>572.569</duration><title>Customizing Your Linear B Settings for Optimal Release Detection 🚀</title><description>In this video, I walk you through the advanced settings in Linear B, focusing on release detection, draft pull requests, and branch exclusions. I emphasize the importance of customizing these settings to ensure clean data, particularly when tracking cycle time and feature branches. I recommend spending time on branch exclusions to avoid inflating cycle time metrics. Additionally, I discuss how we can track coding time based on the first commit or issue state transitions. Please take the time to review these settings and adjust them according to your team&apos;s workflow for optimal results.</description></oembed>