bigmah

These days reading + approving pull requests is a big bottleneck. It used to be the case that it was slower to write code than read it, so the PR queue never piled up. Obviously this is no longer the case due to coding agents. In some cases this does not matter, if nothing is really on the line with a particular repo, reviews can be brief, shoot first ask questions later. But some repos carry real weight. Lots of money is on the line, this is real deal high stakes production software.

In these cases there is no way around a thorough review of the code being released. Of course testing should be as comprehensive as possible, but at the end of the day there are still humans in the loop that are responsible for what a particular program does once released. These humans ought to understand what the code does.

Code review isn't going anywhere.

And the default ways we review code leave a lot to be desired. The stock diff viewer github is slow and hard to look at. The integrated vscode thing is bloated and cumbersome.

Of course we can just checkout a particular PR and view in our local editor, but this can be tedious. what if we have local changes? or want to review multiple branches. inb4 worktree

The path of least resistance today ends up looking like a million browser tabs open, one for each specific thing we want to investigate. The browser makes sense as the place to review things in this way, but we pay the price with ergonomics and a cluttered browser tab list.

pullspace aims to be a solution to this. A better browser based code review UX.

All you need is a github token (or not for a public repo) and then you can open a PR/branch/repo on pullspace.dev where you get a buttery like IDE UX to view code.