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
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 docsCompatibility
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
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.
Blocked: 2 files conflict with origin/main.
resolve them first:
git rebase origin/main
Non-intrusive
Trust
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 GitHubProcess
One command. Native binaries for macOS, Linux, and Windows.
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.
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.