Revset
Review large AI generated PRs as a simple dependency graph
1 follower
Review large AI generated PRs as a simple dependency graph
1 follower
Revset shows your pull request as a graph of the functions, classes and calls that changed. A dependency graph. You see what your agent actually did before opening any code, and the problems become easier to spot: a deleted method that's still called somewhere, a helper nothing uses, a signature change with six callers across four files.
When the agent pushes again, Revset shows only what changed since you last looked, so you don't have to re-read the whole PR.
Hey Product Hunt 👋 I'm Chris, and I'm building DotVCS because
I want a code forge built from the ground up for Jujutsu (JJ) managed repos.
Big tech companies like Google and Meta have been using
similar VCS system internally for years. No branches, everything
is a commit, you stack them, review them one at a time, and
merge them in order. It's pretty simple, and they've built great
internal tooling around it
But there's no public forge built for this model. You end up
forcing JJ's "everything is a commit" paradigm into Git and
GitHub's branch paradigm. All the things that make JJ great
get lost once you push your code.
So I'm building DotVCS. The idea:
Every change is a commit. This is the JJ model
Stacked PR's are a fundamental product expectation, not an add on
Review one commit at a time. Edit one in the middle — all descendants update automatically.
It's early — I'm launching the waitlist to find developers
who use JJ and are looking for a JJ native forge.
Two questions I'd genuinely love your take on:
If you use JJ today, what frustrates you most
about storing your code on GitHub.
If you're aware of JJ but haven't begun using it,
what keeps you from making the change?
Sign for the waitlist at dotvcs.com if this resonates. And I'm here all
day answering questions 👇