<?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/675c0313633f4c50981f203e8d46397c&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/675c0313633f4c50981f203e8d46397c-4470b27224e53db3.gif</thumbnail_url><duration>323.88</duration><title>Testing GitHub Activity Pipeline with Boost</title><description>This Loom demonstrates a GitHub Activity Pipeline test for personal projects by linking a user’s GitHub login to pull Boost-related activity via GraphQL. The presenter creates a “Github” social application with a constant name “testdev” and then links the social account provider “github” to a specific user, switching the login to “Bini Falco” (displayed as “Binifog”). After saving, they return to the localhost profile and confirm the fetched GitHub activity appears for the linked user. They note that expected activity may be lower because the scope is reduced to Boost-related work rather than including other areas like C++ Alliances.</description></oembed>