<?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/1bedc347e0fa4df0a8209ce6c4fc0d51&quot; frameborder=&quot;0&quot; width=&quot;1960&quot; height=&quot;1470&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1470</height><width>1960</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1470</thumbnail_height><thumbnail_width>1960</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/1bedc347e0fa4df0a8209ce6c4fc0d51-bc94e709c8ada362.gif</thumbnail_url><duration>94.692</duration><title>Understanding Risk in Code Merges with RaptorCI 🦖</title><description>In this video, I introduce RaptorCI, a tool designed to help teams identify potential risks in their code before merging. I noticed that many risky changes were slipping through PR reviews and causing issues in production, which is far from ideal. By connecting your GitHub repositories, you can track PR volume and manage developer access and billing. The platform provides a risk score for your code changes, highlighting areas that need attention and suggesting fixes. I encourage you to explore how RaptorCI can improve your code review process.</description></oembed>