Viewing profile — jacobegold

yep we do! another big use case for it seems to be big enterprises for their own internal tools - we see this a lot with our largest customers. but the OSS use case described here …

Not sure how? Meant this: > The agentic coding tools and review tools I want my team (and myself) to have access to are ones that ones that force an explicit knowledge interview & …

Yep. We see this future and are working on exactly what you're talking about (Graphite)

As a Graphite employee, would love this tbh - we love Blacksmith!

Maintained, improved, and integrated. With more resources than ever. We're building whole platform. That's a lot more than just AI.

Correct (Graphite eng here for context) - we've thought about extending our CLI to allow it to sync jj with GH pull requests to do exactly this. Essentially - similar workflow but …

we are a 70 person team, bringing in significant revenue through our product, have widespread usage at massive companies like shopify robinhood etc, this is a MUCH MUCH MUCH differ…

stacked prs will only get better from here :) we have an incredible amount of resources to keep improving that part of our product.

we have a big effort in the works to improve web perf! where specifically are you seeing slowness in the app — what flows, what pages, etc?

My ideal is really just a version of `gt sync` and `gt submit` that handle updating the Graphite + Github server-side of things let you use `jj` for everything else, I think it cou…

It's so cool that Git is considering first class change IDs!! That's huge! This sounds similar to what we had at Facebook to track revisions in Phabricator diffs. Curious if anyone…

hell yeah

(views expressed in this comment are my own, not those of graphite) we have a number of large customers that feel the same way and are fully opted out of anything AI-related. in my…

we still do stacked diffs — it's our bread and butter, and many of our existing customers, some of whom have been with us since the beginning, are finding a ton of value from both …

(Graphite dev here) Yeah – the key thing here is that there is work to be done on the server, so JJ likely either needs its own forge or a GitHub App that handles managing PRs for …

We've already soft launched the next step toward this to some existing Graphite users, so I'm fine sharing! We're adding an agentic chat sidebar to the pull request that can help y…

AI will certainly make human code review easier — the goal being to keep up with the velocity of changes to existing large systems. "Code review" as defined as a human in the loop …

lol. human code review is all we will do day-to-day in a year (i'm the lead engineer on diamond)

a lot? what are the other ones?

I work on the Graphite CLI – curious what you don't like about it and what your flow with raw Git is – I assume you're mostly using `--update-refs`?

I feel like an LLM agent could grok and interact with something like this pretty well...

We (Graphite) love Jujutsu – comes up in conversation all the time here. A prior version of the CLI is open source, the core data model (using git refs to store some extra data abo…

The funny thing is — this is actually different from how OSS (the initial model that Git was built for) worked. Patches are just applied as a single linear commit to the trunk bran…

You don't lose it long term if you're using GitHub PRs — GitHub keeps the "reflog" (quoted because I imagine their implementation may not actually use reflog) of the branch indefin…

Phabricator and Gerrit both do a really good job of this. To me Git works fine as a pure "version control" system, but the process of collaborating on a branch before it gets merge…