<?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/7bc817ff51274739811472af06e351fd&quot; frameborder=&quot;0&quot; width=&quot;1722&quot; height=&quot;1291&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1291</height><width>1722</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1291</thumbnail_height><thumbnail_width>1722</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/7bc817ff51274739811472af06e351fd-41009502b5f78e74.gif</thumbnail_url><duration>608.015</duration><title>Tackle your GitHub Security Alerts backlog via Ona Automations</title><description>In this video, I discuss how we can integrate ONA with GitHub security features to tackle the growing backlog of security issues that our customers face. Many engineers find it tedious to fix these issues, and traditional PR generation often leads to more problems. ONA, with its AI capabilities, can create high-quality fixes and test them in a real development environment before filing a PR, ensuring that the changes are ready to merge. I also demonstrate how to set up automations to streamline this process and encourage you to replicate it in your own repositories using the provided YAML files. Please take action by importing these automations into your ONA organization and modifying them to suit your needs.</description></oembed>