FINDIEA merge engine with one law: main only fast-forwards.
You are watching it run. Every card gets an isolated worktree; a serialized queue lands the work; conflicts park instead of blocking.
0 branches in flight
hold anywhere · 4x time-lapse
Every card opens its own worktree, on its own branch. Your checkout is never the job site.
The graph is the interface.
Findie draws its own topology as it works: branches in flight, the queue, every landing. This is the real screen.
Isolated worktrees
each task builds on its own branch in its own worktree. teardown leaves no trace.
One serial queue
rebase onto the tip, revalidate, squash. one landing at a time, in order.
Conflicts park
a failed rebase steps aside with markers preserved. the line keeps moving.
Idempotent landings
re-runs are detected by durable commit trailers, not by guessing from branch state.
FF or refusal
if main drifted, promotion is refused. the engine never forces, never rewrites.
No force-push. No rewrites.
No exceptions.
Merges happen in a worktree you never see. Your checkout stays exactly yours.
Every landing carries Findie-Task-Id trailers, so retries can prove what already landed.
Promotion waits for a quiet queue. Main never moves while work is mid-flight.
nasıl yapıldı? → rehber (tr)