<?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/806decd9395a47d9bad5b6492d5f4f02&quot; frameborder=&quot;0&quot; width=&quot;1728&quot; height=&quot;1296&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1296</height><width>1728</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1296</thumbnail_height><thumbnail_width>1728</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/806decd9395a47d9bad5b6492d5f4f02-4e271801d11ad73b.gif</thumbnail_url><duration>323.884</duration><title>Resolving Git Conflicts in Branch Sync</title><description>This Loom explains how to resolve Git merge conflicts when two people modify the same file at the same time, especially on binary, image, document, and text files. It describes conflicts arising when the same line is edited in text files, and notes two scenarios: syncing changes on the same branch or merging different branches after both modified the same file. The demo shows resolving a merge state by reviewing side by side diffs, choosing which version to keep for a binary file, and for a text file using options like accept both to resolve specific conflicting lines. It then repeats the process for a branch merge, finishing with a merge commit that combines both changes and can be pushed.</description></oembed>