# \[Open Source\] BranchRift — catch Git integration risk before Unreal branches come back together 

**URL:** <https://forums.unrealengine.com/t/open-source-branchrift-catch-git-integration-risk-before-unreal-branches-come-back-together/2836238>\
**Category:** Pipeline & Plugins\
**Tags:** unreal-engine, unrealengine4, Source-Control, git\
**Created:** [October 1, 2026, 7:58pm UTC](https://forums.unrealengine.com/t/open-source-branchrift-catch-git-integration-risk-before-unreal-branches-come-back-together/2836238 "2026-10-01T19:58:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kaan\_idur](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Kaan\_idur](https://forums.unrealengine.com/u/Kaan_idur)\
**Post date:** [October 1, 2026, 7:58pm UTC](https://forums.unrealengine.com/t/open-source-branchrift-catch-git-integration-risk-before-unreal-branches-come-back-together/2836238/1 "2026-10-01T19:58:31Z")

</div>

Hi everyone,

I’ve been working on a small open-source tool called **BranchRift** after running into a recurring problem in Git-based Unreal workflows: a branch can look ordinary until integration time, while both sides have touched the same map/asset paths or the repository has quietly diverged.

BranchRift is a **read-only Git CLI** that runs before integration and combines a few signals into one report:

- branch topology and merge-base provenance
- ahead / behind counts and fast-forward eligibility
- paths changed on both sides since the merge-base
- binary-sensitive `.uasset` / `.umap` collisions
- Git LFS readiness
- configurable ownership / governance rules
- a focused manual-review and verification list

A “collision” in BranchRift only means **the same repository path changed on both sides since the merge-base**. It does **not** claim that Git will definitely produce a textual merge conflict, and BranchRift does not try to interpret the internal semantics of Unreal binary assets.

It also never merges, checks out, pulls, commits, deletes, or modifies the repository. The goal is simply to make integration risk visible before someone actually performs the integration.

Example:

```auto
Integration:
  Topology: DIVERGED
  Fast-forward eligible: no
  Ahead: 7
  Behind: 4
  Same-path collisions: 2
  Binary-sensitive collisions: 1
    - Content/Maps/L_Main.umap [map, BINARY-SENSITIVE]

```

**Install**

```auto
pipx install branchrift

```

Then:

```auto
branchrift --base main

```

GitHub:

> **[GitHub - Kaan081/branchrift: BranchRift — read-only Git integration risk checks...](https://github.com/Kaan081/branchrift)**
>
> BranchRift — read-only Git integration risk checks for branch divergence, same-path collisions, ownership gaps, and Git LFS readiness.

BranchRift is currently **v0.2.0** , MIT licensed, Python 3.10+, and has no runtime dependencies outside the standard library.

I’m mainly looking for feedback from people actually using **Git / Git LFS with Unreal** , especially small teams.

The questions I care about most are:

- Would these signals be actionable in your workflow?
- Do you already solve this better with locking, Perforce, custom scripts, CI, or something else?
- Does this belong as a local developer check, CI/PR automation, or nowhere at all?
- Is there an important integration risk that this model completely misses?

Negative feedback is useful too. I’d rather find out that the model is wrong than add features around a bad assumption.

Thanks,  
Kaan