Projects on GitHub

Back a project with a GitHub repo so every edit is versioned, with personal branches, pulls, and pull requests to publish.

Klipeo can store a project's history in a GitHub repo. If you've ever used git for code, this will feel familiar: everyone works on their own branch, and changes get merged in through pull requests. It means you can always go back, and two people can edit without stepping on each other.

Connect a repo

First, connect your GitHub account in Integrations. Then, on the project page, press Create <project> repo to make a private GitHub repo for the project. Once it's linked the card shows a Linked badge and an Open on GitHub link.

A few things can stop it:

What you'll see	Why
GitHub account not connected	Connect GitHub in Integrations first
Repo name already in use on GitHub	Pick a different name
Repo already exists for this project	One repo per project

Unlinking the repo also clears everyone's branch records for that project.

What's actually in the repo

Each composition gets a folder of small JSON files rather than one big blob, so two people editing different parts of the edit produce diffs that don't collide:

composition.json — canvas, fps, track order, markers, guides
tracks/video.json, tracks/audio.json, tracks/text.json
overlays/effects.json, overlays/color.json
media/manifest.json

Your media never leaves Klipeo

Media URLs are stripped before anything is committed. The repo holds the edit — timings, tracks, settings, and asset metadata — not your footage and not links to it.

Personal branches

Each collaborator gets their own branch, named editor/<your-github-login>. You edit there, and your work commits there, so your changes don't touch anyone else's until you decide to share them. Branching lives at the project level, so all the compositions in a project ride along on your branch together.

In the editor, a branch pill in the header shows your branch and your role. A blue dot appears on it when the main branch has picked up changes you don't have — Klipeo checks every few minutes and whenever you refocus the tab. Click the pill to open the Collaboration dock.

The Collaboration dock

The dock is the panel where day-to-day collaboration happens:

Commit — write an optional message and commit your current composition to your branch. Leave it blank and you get a default like klipeo: update my-edit (composition #12).
Recent commits — your last commits on this branch, each linking to GitHub.
Pull main — bring in what everyone else has published.
Publish to main — open a pull request from your branch.

Pulling main

Pull main compares your branch against main. If nothing has changed you get "Already up to date with main." Otherwise the Resolve incoming changes dialog opens and you decide, item by item, what wins:

Each changed clip shows Mine and Theirs (main) side by side, with its type, start time, and duration.

Changed tracks, canvas settings, and the media list get the same choice.

Anything you don't touch defaults to theirs — except a clip main deleted that you still have, which stays yours.

Apply, and the merged result saves to your composition and lands as a merge commit on your branch.

Publish with a pull request

When your edits are ready for everyone, press Publish to main to open a pull request from your branch. Klipeo fills in a sensible title and description, and if you already have an open pull request for that branch it reuses it rather than making a duplicate. A link to the PR appears in the dock.

Edit on your personal branch and commit as you go.

Pull main now and then so you're building on the latest.

When it's ready, publish to main and let the team review and merge.

Why git?

It gives you real version history and a clean way to review changes before they land for everyone, without anyone overwriting anyone else. Pair it with collaborators and roles to run a proper team workflow.