<?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/5131782274d14e67a2824846e14f2ea0&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/5131782274d14e67a2824846e14f2ea0-c61ea14c5dbefa87.gif</thumbnail_url><duration>377.91</duration><title>Solving Main Branch Issues</title><description>In this video, I address the warnings and linting issues on our main branch, ensuring all checks are green. I explain the necessary changes made to handle training and generics, and demonstrate the annotation process for task order in crew files. I showcase how tasks are executed in the correct order and the clever workaround used to maintain task order without registration. No action requested, just an overview of the improvements made.</description></oembed>