v0.2 — open source

Push code that merges
and passes.

A git push that first checks your branch still merges with main, and that your tests pass on exactly what you're pushing.

Any language · No config · No history rewrites

What we built

A safety check in front of git push.

pull-pal runs before your push leaves your machine. It checks, in memory, that your branch still merges cleanly with main. Then it runs your test suite against exactly the commit being pushed, not whatever is sitting in your working directory. If either check fails, nothing is pushed.

Read the docs
JS
Go
Py

Compatibility

Works with any language.

pull-pal finds your test command from the project itself: package.json scripts, Cargo.toml, go.mod, pytest config, Maven, Gradle, Make, or Bundler.

No setup per language. Override it with one git config line.

Safety

Blocks conflicts, not progress.

Being behind main is normal, and your CI already tests the merge. What needs your attention is a branch that no longer merges, so that is what pull-pal stops. You get the file names and the command to fix it.

$git push origin my-feature

Blocked: 2 files conflict with origin/main.

resolve them first:

git rebase origin/main

Non-intrusive

Tests what you push. Leaves the rest alone.

  • Never rewrites your history unless you turn rebasing on
  • Tests the commit, not your uncommitted files, then puts them back
  • Skips the suite for a commit that already passed
  • Leaves release branches, and branches you aren't on, alone

Trust

Open source · Local · No config

pull-pal runs on your machine and needs no account. It sends anonymous usage stats (OS, version, whether checks passed), never code, paths, or branch names. Turn them off with pull-pal analytics off or DO_NOT_TRACK=1.

View on GitHub

Process

How it works.

01

Install with npm or Homebrew

One command. Native binaries for macOS, Linux, and Windows.

02

Push with pull-pal, or add the hook

Type pull-pal instead of git push, or run pull-pal setup once and every push from your terminal, IDE, or GUI client is checked.

03

It stops only what would break

A conflict with main or a failing test blocks the push, with the command that fixes it. Everything else goes straight through.

No config file. Every default can be changed with git config.

Catch it before
CI does.

Find out on your machine, not after the pipeline runs.