Bisect

Find the bad commit.
Automatically, in the cloud.

Give Bisect a known-good commit, a known-bad commit, and a test command. It spins up a cloud VM, runs git bisect across your history, and streams the results back. You get the culprit hash in minutes, without burning local CPU.

Get Started View Pricing

GitHub App Integration

Install the app on your repo, mention @bisect-sh in any issue, and get the culprit commit posted right back.

Tests failing on main after deploy #142

Open sarahdev opened this issue · 2 comments

sarahdev commented 2 minutes ago

bisect-sh bot commented 2 minutes ago

Bisect job started

Parameter	Value
Job ID	`j_3kf8x`
Good commit	`v2.3.0`
Bad commit	`HEAD`
Test command	`npm test -- --filter=auth`

I’ll comment with results when the bisect completes.

bisect-sh bot commented just now

Bisect complete

The first bad commit is: a1b2c3d4e5f6

a1b2c3d4e5f6789012345678901234567890abcd is the first bad commit

Detail	Value
Job ID	`j_3kf8x`
Status	completed
Exit code	1

Output (last 2000 chars)

$ npm test -- --filter=auth > [email protected] test > jest --filter=auth FAIL tests/auth.test.js Auth middleware ✓ should parse bearer token (3ms) ✓ should reject expired token (2ms) ✗ should validate token refresh (8ms) ● Auth middleware › should validate token refresh expect(received).toBe(expected) Expected: true Received: false 42 | const result = validateRefresh(token); 43 | expect(result.valid).toBe(true); | ^ 44 | }); Tests: 1 failed, 23 passed, 24 total

🏷️

bisect-sh bot added the bisect:found label

bisect-sh bot closed this as completed

Get Started →

Any Test Command

Pass any shell command: a test suite, a build, a curl check. Add --setup-cmd to install deps before each step. If it exits non-zero, the commit is bad.

Zero-Config Runtimes

Bisect auto-detects your project from lockfiles and installs the right runtime: Node, Python, Rust, Go, Ruby, Java, .NET, and more. No Dockerfiles needed.

Pick Your Instance