pando
One repo. Every branch alive.
Every branch you are working on, running at once: each in its own checkout, on its own ports, with its own logs and, if you want, its own database. All on one terminal screen.
brew install mertkaradayi/tap/pando
then run pando in any project · other ways to install · read the docs
macOS · Linux · Windows with WSL 2 · free and open source
Fishlake National Forest, Utah
It looks like a forest.
It is one tree.
Pando is a grove of quaking aspen. Its roughly 47,000 trunks all grow from one root system, which makes it a single living thing, and the heaviest known on Earth. Its name is Latin for “I spread”.
trunk → branch · root → repository
Your repository grows the same way.
Git can check out many branches side by side, each in a folder of its own, all sharing one history. Git calls these checkouts worktrees. Your repository is the root; every branch can be a trunk.
one checkout · one port 3000 · one branch at a time
But in one checkout,
branches take turns.
To look at another branch you stash, switch, reinstall and restart, and the port is still taken. Its migrations land in the database you were using. To show a teammate, it goes to staging first. Then you do it all again to come back.
so I built pando, for my own work first · Mert Karadayi
pando lets every branch run at once.
Each branch you work on gets a checkout of its own, already running, on ports no other branch uses. You see all of them on one screen, and switching branches stops being a chore.